You should be aware that Blizzard/Microsoft make changes to Battle.net somewhat often, and they have a habit of breaking it in Wine. It might work fine for a week or a year, only to get an update and suddenly misbehave or fail completely until the community has time to figure out what changed and develop a fix.
On a few occasions, the breakage has been in a new version of drive_c/ProgramData/Battle.net/Agent/Agent.*. People who still had the older version installed were able to work around it by removing all permissions from the new version’s directory and marking it immutable with chattr. Battle.net then fell back to using the previous version, allowing games to run until a fix in Wine was developed.
Also, fixes make it into some Wine variants faster than others. For example, last time I dealt with this stuff, I found that the GE-Proton9-27 build of Wine handled Blizzard games pretty well while others did not.
With all that in mind, I wonder if the problems you’ve been seeing are not rooted in your Vulkan drivers, but instead the usual pattern of Battle.net updates fighting with Wine. It’s possible that you’ll just have to accept Blizzard games breaking on Linux every once in a while, and when they do, updating the Wine runner you use in Lutris when one with a fix becomes available.
I wish the filters and most housings weren’t made of plastic.