Programming languages and standard libraries are written in English, programming terminology is invented in English, the international community adopted english as a defacto standard, almost all third party APIs expose English interfaces.
Every time I've seen a project written in my native language it's been ridiculously hard to follow because the terminology is translated in various ways (there's no official or even widely used terms because hardly anyone uses native language in SW development and CS outside of academia) and it's a mish mash between languages since everything not written in the project (along with language keywords) is written in English.
I don't usually take a hardline stances on things but this is one thing where it would be 100% a dealbreaker for working on a project.
And outside the western hemisphere where off course if the code base is unlikely cross, say, outside the Chinese borders, where Mandarin would be more appropriate.
Then there are non-industrial standard codebases, say a hobby project. I’m sure that somewhere in Guinea-Bissau there is a 17 year old learning Python at this moment, really happy that they can write Portuguese special characters as variable names in python 3 (if only the documentation had been translated to Portuguese).
Just because English is the appropriate language in by far the majority of cases, does’t mean we should deny the possibility of not using it.
The allowed set of characters would have to be vetted very carefully before I'd consider non-ASCII.
Edit: A small taste of what we can expect: https://i.imgur.com/k8S00sM.jpg
Also, bugs caused by accidental homographs in identifier names are caught by any reasonable type system, just like any typos. As for your edit, you can't stop clever people being clever without code reviews anyway, no matter what the language.
Unicode maintains a list of these characters (homographs), and Rust rejects them / warns on them.