You're not going to get the world of Java, C, and C++ coders to change to a monocase font. First, and most importantly, they won't because they simply won't. It doesn't matter how many logical arguments you throw at it, how many facts or figures you present to back up your case, how much sympathy you garner from any social group, or even if you got some candidate to introduce new laws mandating the use of all uppercase alphabets in programming languages. You'd actually have much better luck introducing a new case-insensitive language to the world and getting a thousand people to adopt it. It's so ludicrous it's not even an interesting thought experiment. Trying to convince anyone that this is a viable idea is nothing but wasted time. So please stop, right now.
Instead, let's look at alternative ways to make the problem more tolerable at your end.
How about a screen reader that switches voice for upper case; reading lower case text in a higher register and upper case text in a lower register? How about adding case-words to the vocabulary, such as prefixing any upper case letter with CAP- . What about other sounds? How about or one beep to introduce uppercase, and two beeps to introduce lowercase? Or how about a subtle background sound that plays only while it's speaking upper case characters; something like a static hiss that would serve as an audible indicator?
Or better yet, how about a meet in the middle approach: an IDE that fully understands your needs with regard to case, and refactors the code as it imports it. It would make the kinds of substitutions that would remove the reliance on case. It could automatically refactor WindowManager to CAP_W_INDOW_CAP_M_ANAGER, or following the rules you were trying to impose above, or whatever. Perhaps it could simply monocase everything for you, and be smart enough to know the differences from context. You could type your code without regard to case, and build and test it at your leisure. When your normal screen reader speaks the code, it already ignores case, so no changes there. When the IDE builds the code, or when you check it in or merge it, the IDE would refactor your changes back into the original case so the rest of the world is none the wiser.