Earlier quoted context omitted.
What's insane here? Waking the machine up is a legitimate use case, and it's easily traceable and configurable.
A machine doing something I didn't tell it to is insane. I am the user. I use the machine, not the other way around.
And running a configuration command is in fact you telling it what to do.
So the actual issue is open-systems vs walled-gardens in system design and how it surfaces in consumer products. The only thing Windows can do is force you to review each and every device driver on install for e.g. can wake machine. A non-starter for a consumer OS.