How would NetLoadModule know what the newest versions were for each module? Right now anyone can drop module zips on a server and use it as a module archive. (I've shared the zip dir on one machine and used it as an archive for another.)

Modules will break compatibility between versions from time to time. What are you going to do to prevent it, fire the developer? Nobody's paying developers to think ahead when they design their configuration so that it will seamlessly support new features.

Similarly, expecting them to make note of compatibility changes is naive, you're lucky the documentation is kept accurate and up to date. Sometimes compat. breaks unintentionally too.

The bottom line is that there's more work involved in "fixing" this than in just dealing with it, and that work would have to be done by those spread the thinnest.