The mere existence of such an api would be an interesting source of problems when used accidentally/via buggy code ...
I wonder the degree to which this functionality would end up becoming relied on as a "in worst case hard kill things to recover" behavior that folks utilize for bad engineering reasons as opposed to good ones ...
In a previous job we actually had to make a decision like this: our server software was generally stable enough, but we reset it whenever we did an update. Every once in a while it would break when running for long enough.
I opted for forcefully restarting the software every day, because I'd rather relive the pains of restarting, than to discover in production what it is like for the first time to run the system for the 501st day of uptime.
(To be honest, the system in question was mostly written in Erlang, so controlled restarts were already baked into its philosophy.)
Edit: Another term is Switched PDU
This would be more effective if so many other AWS features weren't hidden in non-obvious places in the docs.
On top of keeping people who don't want it out, you'd need it to be expensive to offset the lower utilization.
I'd be okay with a garbage-tier, too. It's not failing on purpose, but only because no one gives a shit. Maybe that's just standard AWS?