Well sure, I'm talking about vkd3d-shader side already, whether we want this option exposed and documented for any vkd3d_shader_compile() user, or make it into something internal.
I don't understand? It already is exposed and documented. We can't remove it.
I don't see how any end user of vkd3d-shader, outside of wine, would think of using any of those custom options.
I can't say I see it as likely either, but giving vkd3d-utils a secret unstable window into vkd3d-shader seems unnecessary for a case like this.
Also I'm surprised we ended up having any logic involving windows module version numbering in vkd3d-shader.
As Matteo says it's not in vkd3d-shader; it's in vkd3d-utils.