https://bugs.winehq.org/show_bug.cgi?id=50542
--- Comment #3 from Liam Middlebrook loothelion@nvidia.com --- I think that logic makes sense. Although maybe this is a staging-level patch?
A Vulkan Device selection layer should be affecting this section of code in winex11.drv also, not just the application+winevulkan. If users aren't seeing any changes from enabling it, I'd think there may be something in the newer Proton versions which make use of a container-based runtime that just isn't importing the device selection layer properly.
In upstream I think it's important to respect what order the VkPhysicalDevice entries are being supplied to us in.