To my knowledge, both the username and email fields are treated as case insensitive (lower cased at creation time) and there’s no configuration toggle available that would allow to do it differently.
Depending on the exact scenario storing the original case sensitive version as part of user metadata may or may not help in achieving a possible workaround, however, I wanted to throw that on the table in case it’s helpful for your particular scenario.