Modularity means easily moved from one location to another. The problem is that integration defeats the modular approach. Integration disallows the thing you are looking for: Plug n' Play.
Modularity is what allows for a user to just set it up and have it work.
Diversity - this is the other matter. I think some Windows OS users have the mindset of avoiding choice paralysis by allowing their choices to be limited. They do not want to have to deal with learning the system; they want to just turn on the system and have it work for them.
However, this stereotype is atypical. It is often cited, it is even self-claimed; but the majority of users that actually seek out help, answers or other customizations all express that they want choices, even when the stereotype is applied to them - even when their own words say that they "just want it to work."
I believe that this is because Microsoft, Google, Facebook and other powers-that-be teach the concept of the ever marketable "you just want it to work." It is not what people actually want. It is what they are told that they want. And there is a difference.
Never is this difference more stark than once you set a person up working and they start actually trying to apply what they want but are balked by a system set up to "just work" or in other words: Limit User Controls.
This is why teaching those users and helping them to understand their capabilities and to enhance and increase their learning is more important than just applying Microsoft/Google/Facebook doctrine to them.
The ZorinGroup is remarkably tolerant - to the point of creating confusion, even.
I agree that the tolerance is admirable. But it also has led some to the conclusion that the ZorinGroup is detached and apathetic - an answer to which remains unclear.
I would be surprised if they were capable of reviewing and applying user feedback in the way that they do if there is apathy.