There’s more to it. It wasn’t Play Integrity blocking Graphene per se, but the fact that Revolut checked the build ID string, which was uniquely identifiable as Graphene for any build. This was then made more generic, so the block doesn’t work for now, but the workaround could break any moment and be made impossible by Revolut enforcing “strong” level of Play Integrity. Such bullshit.
The PS3 is such a nice console. There is something special about using a device with such unorthodox CPU (Cell BE), especially when you see it running graphics intensive games in (relatively) high fidelity, like The Last Of Us. The console only has 512Mb RAM and 256Mb VRAM, and the GPU equivalent of the 8600GT! But due to the architecture of the Cell BE, a lot of the graphics processing was performed on the SPEs, so basically on the CPU instead of the GPU.
There’s also the option of using Private Space (Android 15+) or its multiple clones in manufacturer OSes. It effectively creates a new user profile which can be deactivated at will. The new user profile also has no access to any data from the main profile that can’t already be controlled by permissions, like the app list. It has its own instance of Play Services, so AFAIK it shouldn’t be linkable to the main profile. It’s the best middle-ground I’ve found this far if the app needs to be installed in one way or the other.