I guess a language- and compiler recommended style guide that a lot of people follow increases the value of the eco-system as a whole - just like a single developer is likely to output similar code and benefit from the familiarity that this brings, a whole community come together and do so, decreasing needless friction between libraries and making it more pleasant to use code from multiple sources.
Thus, a system that's good for the community is one that guides the novice towards a safe and globally beneficial defaults, while it allows the master the freedom to step outside those bounds so as not to become a constraint. Seen through this lens, the case insensitivity feature does not really have to be removed - it simply can be hidden behind an option that allows you to turn it on when appropriate.
