This is why the term "patches" is a poor choice to describe security updates. Most of the time, they DO fix the root problem rather than being a temporary fix. Usually mitigations for known vulnerabilities are more analogous to a patch, since they are ways to avoid getting exploited in the absense of a fix.Patches aren't perfect, NO software is, let's be clear about that. Patches can only work so long for so good before you need to plug the hole again. So instead of sticking a band aid on a wound over and over again, trying to fix the problem, get at the root instead!
Ever hear of the phrase "do as I say, not as I do"? This is essentially what you are telling your clients; you are saying you know better than them, so you don't need the security updates. You probably DO know better than them, but that doesn't mean you shouldn't install security updates. One's knowledge and the need to apply security fixes are not mutally exclusive. Every security expert worth anything practices secure computing, which is basically what you are describing. But they also install security updates.With what I know, what I do, I can do the things I do. NOW did I say that was for everyone? NO.
Yes, you can get burned by a fix that causes other problems. This is why you test. Microsoft spends a LOT of time testing updates before they are released in the wild, but there are far too many combinations of software and hardware out there for them to catch every possible regression.