There are 2.5 billion Android devices out there and only 5 million people have ever installed Termux, let alone compiled and run their own binaries. Would you, as a developer, implement a workaround for disabling an OS security mechanism for _at most_ 0.2% of your user base, most of which will probably work around it themselves by flashing an Magisk module anyway? What about the need to validate and maintain the workaround so that malicious apps can't find a vulnerability to disable the feature themselves? It doesn't make business sense to me. Android is already full of backwards compatibility hacks to make sure apps don't break too quickly, especially when they're doing stuff that you wouldn't expect.
App developers can still provide modules to the Play Store (grouped packages can access each other's data as far as I know) so the most valid use case I can think of aside from compiling your own code (optional video codecs) would already be covered. Python interpreters and Java runtimes would work just fine as well, so programmers whipping up a quick program on their tablets are still able to do so.
The only victim are people who compile their own binaries on their phones. I don't think their use case is worth risking disabling a very valid security mechanism.
I wouldn't write the code to disable the functionality of the device.
Obviously, that means I wouldn't end up on the team to begin with. So it goes.
Only?
Granted, it's Google, who makes that kind of evaluation (see also: killing products that could be a whole company because they "Google scale"), but it still seems like throwing away that many users is eventually going to come back to bite them.
Just because someone installs an app doesn't mean they use it every day. Reading the reviews, most people seem to just use it as a basic terminal emulator, like there are so many on the play store.
Those people aren't going to notice anything about no longer being able to compile executables.
If you package the compiler with termux and output the APK to a shared location, nothing about this article will change after Google's future modification.
And I don't think a few users getting abused with this trick is sufficient enough to remove the feature altogether, that's their device after all. The alternative of removing everything seems much worse.