Honest question: On most OSes, don't regular drawing operations in these programs (Bitblits, font renderings) typically use hardware acceleration through the OS? On crostini, are these things currently done via pure CPU operations, or are they already being mapped to hardware-accelerated API calls, even before the new OpenGL support?
For other operating systems, the words and details change, but the overall idea of "it's complicated and depends on your driver and OS version and which apps are running and phase of the moon" still applies.
God knows if Xwayland will incorporate GLAMOR. Since almost all compositors except for Weston assume the presence of a GPU, you'd think it would, but I have not been delighted with Wayland development thus far...
It works by having the guest run a Mesa3D (Linux Userspace graphics) driver called virgl in the guest, which takes all of the OpenGL/OpenGL ES commands and send them through through Linux VirtIO[3] to the guest, where they are executed by the virglrenderer[1] application as normal OpenGL / OpenGL ES commands.
This let's you run whichever driver you want on the host, even proprietary ones. And it allows you you to do transparent OpenGL <-> OpenGL ES translation.
[1] https://gitlab.freedesktop.org/virgl/virglrenderer/
[2] https://www.mesa3d.org/
[3] https://lwn.net/Articles/239238/