I'm really curious about how you use it, because for me it was braindead. I tried tasking it to update my personal workout app and it created so many bugs I had to clean up with Opus or be left with spaghetti. It also keeps asking for confirmation of doing basic things.
Your shipping container mention reminded me of The Box, a book that explains how shipping was so erratic, risky, slow, unreliable and incredibly expensive before the standardization into containers. Containers literally changed the world economy.
I think you are onto something. But this requires upfront investment, which alas, politicians are not for.
Managing shared memory is not a new thing for Apple, as it has been doing the same on iOS for a long time. Maybe a bug in Monterey? None of the M1 users I know had this issue.
My point is that if there is any downtime for the switch, for example restarting a service, it's not atomic. A small percentage of failed requests can still be high in absolute terms for a company like Slack, so why not using a paradigm [1] where you have atomic switch? And also instant rollback.