I love that they start no no core pinning, then switch-over to having cores pinned.

This could be a bit of a tricky one, but I'd expect Checkpoint Restore In Userspace eventually tackles a lot of this. An image of a running Chromium process on a tmpfs (in-memory filesystem) that can just be launched endlessly tackles the memory slowdown problem, eliminates conventional startup costs. This feels like an ideal CRIU use case.

I imagine there's a lot of things Chrome needs to run though, bits of state to save/restore.