You're talking about a fundamentally different situation to the rest of us here.
In your example, a remote service on which some functionality depended was disabled. Obviously anything that depends on some remote facility can be affected by changes there, regardless of changes to the local machine. This is a real danger of the kind of always-online systems we have today, and it can be (and certainly has been) abused by developers, but I don't think it was what the rest of us were talking about in this particular discussion.
What we were talking about before was whether Microsoft could forcibly affect a Windows 7 system itself to disable functionality, analogously to the Windows 10 updates that started this discussion. The only change to a local machine in your example appears to be via a software update, which you can choose not to install on Windows 7, while not everyone on Windows 10 has that option, short of actively circumventing Microsoft's system.
The Anniversary update for Windows 10 is particularly troubling, because up to now the only way to restore some of the control that earlier versions of Windows offered (notably including controlling Windows updates themselves) on Windows 10 Pro has been through group policies, and Microsoft have now demonstrated that they are willing to remove even that control mechanism if it suits them.