On the other hand, I see a developer's tools as an extension of his or her mind. Enforcing that everyone uses the same tools seems like a great way to encourage hive mind thinking.
Especially proprietary tools that can not be automated or extended is something you should be wary of pushing onto for example a bash and vim wielding programmer, unless your business has no need for major productivity gains to grow or to sustain itself.
I don't encourage hive mind, by other means. The proprietary tools I recently used where automatable with either apple script system or in java for jetbrain product, but generaly we would do a lot of command line automation because we are more proficient in that. And I try to push products designed for their users instead of designed for their licence or their developers to my product team. But also i leave the freedom to my team to change the tools, every wednesday, we can change some tools, for the whole team.
Especially proprietary tools that can not be automated or extended is something you should be wary of pushing onto for example a bash and vim wielding programmer, unless your business has no need for major productivity gains to grow or to sustain itself.