It's perhaps worth pointing out that even if Wine's DXGI were to stop using vkd3d_acquire_vk_queue(), that wouldn't make the API go away.
Is there any hope that we can deprecate it and eventually make it go away? I think it's basically a broken API, since it lets clients access internal vkd3d data at a level which is too low to make it safely usable. It was probably good enough before the CS queue was introduced, but I don't think there is any reasonable way to have it together with the CS queue, which is essentially where the presentation order bug comes from. So I think we should deprecate it anyway, as soon as we give our clients some way to do the stuff they wanted to do with it.
However, that's a rather orthogonal question: this MR still fixes a bug, and if we eventually want to switch to a worker thread (either by breaking compatibility or making the worked thread optional, so that `vkd3d_acquire_vk_queue()` can still be used by clients that don't want to use the worker thread) that's made easier by this MR as well.