I’m just saying the “steamlib proxy” concept you mentioned is not only possible but has at least one implementation. The fact that Wine isn’t true isolation doesn’t really change anything (maybe other than the exact details of the underlying IPC channel, which could use some kind of optimized shared memory magic) unless I’m misunderstanding something.

Some games will probably actually rely on Steam, like for achievements or something. For those…If there are a substantial number of Mac games that won’t work in a 64-bit environment, I am wondering if it is possible to make a “steamlib proxy” – basically, have a 32-Mac VM, run the game in a VM, but have Steam running in a 64-bit host environment, and just relay calls to a process launched under the host environment that uses the host steamlib to talk to Steam. Valve presumably isn’t gonna set that up as a supported environment, but I wonder if that might be a viable open-source project.

I think Proton has something of that nature, so games running inside Wine talk to the native Linux Steam binary.

GrapheneOS is the extremely paranoid security-above-literally-anything-else ROM so of course they’d say it’s a bad idea.

The TLDR is that, without special protection (bootloader relocking, which is the reason why Graphene only supports the extremely limited amount of devices it does), rooting and bootloader unlocking intentionally punches holes in Android’s security model in exchange for greater control.