We our our RMM patcher wait till Friday to push out the updates. Gives Microsoft a couple of days to recognize a bad patch, pull it, fix it, and re-release it. And if we know about a "bad" patch, we can deny it. before it goes out.
No way we have time to "test" every patch released either. I've seen some IT people claim that do that...LOL...I raise an eyebrow in dis belief that they have THAT much time to go and test every patch with lots of variables and mixed matched software to vet it out.
I am a believer in keeping systems patched.
I will say however, I have had to fix damage from bad patches. I don't have a number of how many clients of ours are "not managed" (thus not on our patching system)...but I'd wager it's over 700-800 devices, and a few dozen servers. One bum update that tanks something on a server can make a miserable week or two for ya. I can recall a recent example that gave us a hell week-ish couple of weeks...those two bad updates over the past year or so which broke print servers.
But the goal is to fix more problems by installing updates rather quickly, and hopefully very rarely..have to deal with issues resulting from a bad update.