In this case, you might be glad to learn that PowerShell is case-insensitive, even for CLR methods.

Are underscores/dashes coalesced out too?

There are aliases, you can name things with a letter if you want. There are even good ones OTB.

Most builtins are aliased:

    Get-ChildItem == gci

I greatly dislike case-insensitivity. It's a source of many problems for users and implementors.

For implementors case-insensitivity means the need for full Unicode support is urgent, while Unicode canonical equivalence does not often make the need for full Unicode support urgent. In practice one often sees case-insensitivity for ASCII, and later when full Unicode support is added you either have to have a backwards compatibility break or new functions/operators/whatever to support Unicode case insensitivity.

For users case-insensitivity can be surprising.

For code reviewers having to constantly be on the lookup for accidental symbol aliasing via case insensitivity is a real pain.

Just say no to case insensitivity.