I really don’t care enough to try and actually make converts here. It would have been a perfectly justifiable design choice to make our “pattern” matching case-insensitive by default, probably with a case-sensitive mode and no need to hack up quoting rules that are unique to it. It’s a find feature and search benefits from case-insensitivity. There isn’t anything so compelling about the current behavior that it seems like the superior choice. But maybe you are right and I just lack sufficient real-world experience to see things differently.
I also get not wanting to change behavior at this point though I’d welcome a modifier like “*” (like the ~* operator) to enable case-insensitive matching.