gVisor is used in a lot of places[1] that require more performance than a clock. I'm not saying you can't achieve more performance with C++/rust, what I'm saying is that this probably isn't the primary concern.
1. https://cloud.google.com/kubernetes-engine/docs/concepts/san...
https://gvisor.dev/docs/architecture_guide/performance/#netw...
Network performance in gvisor is awful and, by gvisor's own documentation, this is a matter of "implementation costs" ie: it is how gvisor is written, not gvisor's fundamental constructs, that makes it slow.
The rest of the benchmarks are notable as well, there are a few other places where the implementation is called out as being a problem.
1. It's designed to run on Fuschia, not Linux
2. Go FFI is very inefficient, you can't just "extend" a Go project with native bindings and get the same performance wins
3. Hopefully the gvisor team learned the obvious lesson that Go is not suitable for this kind of work
You mean you'd like to read a source to back up that statement.
Nothing is required...