I think you'll find that we don't keep a lot of things secret about CPython and its implementation.
Yeah, I agree that this is in principal a good thing and what makes CPython ideally suited for research. However, my optimizations make use of unused opcodes, which might be used in the future by actual CPython instructions (e.g., from my previous patch to the new one the YIELD_FROM instruction has been added.) I'd say the situation is similar to the threaded code/computed goto's issue.
Although this is different when it comes to the community. The PSU has
I am going to file a patch like Martin von Loewis suggested.