I think we’re misunderstanding eachother. So perhaps consider to outline if you agree with the following:

• uBlue has some systems in place that enable it to detect some breakages.
• uBlue’s pipeline is such to not ship you the detected breakages.
• After a method has been found to fix a breakage (or other issues), uBlue’s maintainers implement these fixes and then, the very next update, the users will receive an image that contains both the updated package and the fixes required for it to not cause problems. Heck, the user didn’t know anything was up in the first place. They didn’t notice a thing*.
• uBlue’s issue/problem detect systems are not absolute; things might slip through.
• However, Nvidia drivers will not cause breakage that will make you shiver in fear.
• uBlue does not fix it on your device. They fix the image and that fixed image will deliver you the fix built-in; so manual intervention are a thing of the past (except for edge cases).
• Their pipeline does not require nor does it detect (through telemetry or whatsoever) the breakage on the device of the user. Heck, as implied earlier, most breakages are detected, prevented from shipping broken, fixed, ship the fixed one before any end user is disturbed by it.
• uBlue is not a Stable system (i.e. it does not freeze packages (apart from security updates) until the next major release). So yes, you receive updates all the time.
• Not being tied to legal restrictions is cool. However, a lot of derivatives do this. So this can’t be its unique selling point.
• uBlue is not entirely free. Its maintainers do pay money for providing some of their services (as has been mentioned by Jorge).
• Some of their images do have testing branch; even Bazzite has.