Yes, you can reason about safety in just the same way, as long as a safe API is built around the unsafe usage. That’s why you can have safe OpenGL bindings even though the underlying raw C calls are unsafe
E.g. https://github.com/glium/glium
Rust would be useless if you couldn’t have safety if you had any unsafe at any point. That’s the whole point of rust: you can build safe interfaces to unsafe actions
This is totally on my radar. I want to compile to wasm and target WebGL. I'm using https://github.com/glium/glium/ to target OpenGL on Windows, Mac, and Linux right now. I've been meaning to check out https://github.com/grovesNL/glow/, which also supports WebGL.
For Rust, there's [1] for OpenGL and [2] for Vulkan.
I don't know about Vulkano, but Glium is much more pleasant to use than the raw OpenGL API.
RQBG does not generate bindings for that, but you could derive from QOpenGLWidget and write FFI to call into Rust for painting and resizing. Then you'd use Glium to do the painting. You can still use RQBG for the application logic.