I think you're saying you intentionally use an unpatched OS with known actively exploited and patchable vulnerabilities, you do so in situations where the machine is connected to the public internet, and you think the thing you should be worried about is Microsoft attacking your machine via Windows Update.
I don't think you need to worry about the number of people wanting to replicate your configuration exceeding the load your micro instance can handle.
> you do so in situations where the machine is connected to the public internet
Where'd you get that from? My "micro instance" is clearly not on my Windows machine. My Windows box is behind a pretty over-the-top firewall (which isn't even necessary on a private network for the exploits that are public). Not every vulnerability makes you remotely vulnerable behind your NAT, and I wish more of the people obsessed with update-hygiene understood that.
Is my solution good for a corporate network? Obviously not, because you can't control the attack surface.
I don't think you need to worry about the number of people wanting to replicate your configuration exceeding the load your micro instance can handle.