I ported it to Fedora, not just for my specific system, so anyone running Fedora can use it. It’s not available on Fedora right now, and I don’t think they’ll ever port it themselves, since it’s a bare-minimum policy. You need a dedicated SELinux policy for your WM to actually benefit from the Wayland policy.
Yep 
I even ported the WM’s SELinux policy 
See my answer above
- I use github[.]com/cage-kiosk/cage inside for the GUI
- The lifecycle is managed by systemd. When I open the desktop entry the VM starts; when the window is closed the VM stops
- streamlined debian inside crosvm
- I use ext4 for FS. btrfs has no benefit in this case
- You can optionally also use bubblewrap and seccomp inside the VM. There is already a sandbox and seccomp outside the VM, called minijail, so you don’t need one outside
- crosvm’s Wayland display backend with
virtio-gpu backend=2d
I did not try sounds, so I am not sure either. The isolated electron apps I use did not need sound, and I never used sound in the isolated Tor browser either. I did not put my main browser in this VM.