Earlier quoted context omitted.
There's no shame in being homogenous and obvious, though. If I'm building out an internal tool for, say, a hospital lawyer to search through malpractice lawsuits, I want my tool to be the most familiar, obvious, least-surprising UI/UX possible. Just stay out of the way and do what it's supposed to do. The trick is, of course, that the human is still responsible for knowing when homogenous is fine, or when there's rea…
There's a real problem with everything looking the same though. For a consumer product, you lose brand recognition. For a B2B product, you can confuse your users because Tool A and Tool B look exactly the same. You have to look hard at the name, kind of like prescription pill bottles.
Apple/SwiftUI has accentColor for example where you can inject a brand colour. This is subtle but effective for UI differentiation - colour is a design primitive that evokes subconscious pattern recognition and can be more effective than a complicated design framework that forces a larger context switch in the user's mind.