matchboxbananasynergy I continue to doubt that this has reached the development team. I might be wrong, however.
Proton support sent me the following, on Sep 11:
The Android development team is already aware of some crashes happening with WireGuard due to memory corruption, and they're actively being looked into.
Unless they are not speaking truth, I have to assume that the sentence means it has, at some point, reached the ears of a development team. Although "some crashes" is vague enough to not aspire much confidence that the support team relayed my emails to the development team, it sounds like at least some memory corruption was being looked into at some point in the past.
Extremely frustrating that a company heavily marketed towards privacy continue to not prioritize this (but at least we now have confirmation of that). Also does not inspire confidence that, with the exception of Proton Pass, all their apps have obvious incompatibilities when being run with memory tagging. A direct competitor has fixed a memory safety issue reported by a GrapheneOS user and is now running their Android app with memory tagging on GrapheneOS in order to debug further issues. That appears to be in stark contrast to what Proton is doing. I will be relaying the Go bug to them, then I will give up on their support team. Someone else is welcome to pick up the ball!
Wishing you all a happy day.
(And thank you for your patience with my expressed frustration!).