Oh sure, I hear ya. There are, indeed, many moving cogs to the V8 that is a web server. I've seen doozies in my lifetime. For example, we are bringing our servers up to the CF 10 Lockdown Guide as far as Best Practices go. But if you add all the Request Filtering for the URL sequences, you actually break ColdFusion from performing updates. We found the keys that need to be removed, and on the site that has access to CFIDE, we removed that key and it works fine. Troubleshooting skills pay off in spades. 
I do hate the "It works all of a sudden, I didn't change a thing!" situations, because there's no comprehension of what caused the issue, nor knowledge and experience gained from having resolved (and subsequently made a tech note) of it. I have found that one of the skills I need to enhance is my ability to comprehend the HTTP process from beginning to end. Not a concept often spoken of, and when it is, it usually is a combo of how it is with PHP or .NET.
By the way, I make a scheduled task called "Dot Net Nuke" which looks for "aspnet_client" folders anywhere on my server and if they're not in a whitelist, deletes them, every hour, on the hour, indefinitely. That accursed folder shows up all over the darn place like a virus, and I finally got sick of Microsoft's sloppy coding practice. We have .NET supported because of a handful of 3rd part apps, but it's amazing how much that damned folder propagates itself into sites, folders, and subfolders that have nothing to do with .NET code.
I'll run the option by my supervisors and see if they'll spring for it. Thanks for the offer, Charlie.