May be fine for small, isolated projects, but when you are dealing with a whole ecosystem of re-usable modules that can be recombined in any number of ways, internal consistency is just as important as 'my concrete thingy passes the unit test'.
From their perspective you may be creating an e-bureaucracy that only you or a handful of architects fully understand. It gives you the sense of power but slows them down because they can't grasp your "ecosystem" or libraries quickly.
And when they complain you perhaps tell them "be smarter and spend more time learning them, or quit so we can hire faster library grokkers".
That's how communism (or extreme socialism) viewed economic systems: factor everything into as few parts as possible (parsimony) for efficiency and consistency. You don't need 5 brands of peanut-butter like those market nations have.
It sounded wonderful on paper, but did poorly in practice (except for the top-level bureaucrats).
Sometimes reinventing the wheel is more efficient for humans than grokking and managing a Department of Wheels. Perhaps such duplication working is counter-intuitive, but hey, some things just are.