I investigated this. It seems like we are okay for now. We'll want to revisit this once we no longer need the prototype.

Context:

While setting up the prototype, we added an exception to blocking calls so we could load the dynamic library: https://cs.chromium.org/chromium/src/content/browser/compositor/gpu_process_transport_factory.cc?l=1035&rcl=7a954e099711e68c3bad517777f0867127247bc3

This made it obvious that we need to initialize Vulkan in the correct place.

While investigating the correct place to initialize I found there already is Vulkan initialization there: https://cs.chromium.org/chromium/src/gpu/ipc/service/gpu_init.cc?l=183&rcl=2f3569a4f414b420349e6251721c84bdea8fac4e
The catch is, this is never actually being hit. I suspect as work on OOP-D + Vulkan progresses it will eventually be hit.

Once we no longer need the prototype we can remove the exception to blocking calls. Until then, I think this is on pause.