Well, as proven a lot of times, drivers and games don't really 'need' to have "worked together", only tripple A games really even work with the producers, there's a lot of games out there that have had very little talk with devs because they stay within parameters that are defined in the API's, the only advantage driver talk does is optimization, but optimization doesn't mean you go from 10 to 60 fps, an issue like that means there's a problem in game or in how the api handles specific calls and calculations..
And this is the 'problem' with AMD in general, namely how they handle these things in the driver, why they do it the way they do? who knows, and I couldn't pretend to know where the real issue is.
But it seems fairly consistent in terms of issues, that AMD a lot of times has to release a new drivers with 'fixes' to get some games working at all. Where even with a game optimized for AMD, nvidia's drivers will do just fine, only having issues with proprietary stuff, such as the hair fx's in tomb raider.
So yeah, am I saying AMD is a bad product? no, that's why I state it as 'problem' because most of the time, any potential problems are caught before release.
But AMD has their own way of doing drivers which historically has lead to weird issues.
Nvidia hasn't been perfect themselves, but their issues have more been crashes and similar rather then performance issues.
But yeah ultimately only the creators of the drivers know what is going on in either of the cases, we outsiders can only see the results.
As for Vulkan, hate to break it to you, but Mac will not be getting Vulkan support, Apple has decided not to adopt it, so no vulkan for Mac's.......unless maybe people poked Apple enough to make them reconsider said weird choice, but given their history with OpenGL....yeah I'm not that hopeful.
That said there are some that are trying to create a layer between metal and vulkan:
https://moltengl.com/moltenvk/
But yeah, why Apple themselves don't add support I don't get.