I would take results from adapters/emulators like DXVK with a pinch of salt. They might seem faster but due to the nature of the emulation they might not be producing visually identical results. For example in cases of features or limits not supported by Vulkan but supported by D3D12 the adapter might feed this back to the application that the feature is not supported causing the application to take different logic paths and so skip potentially demanding operations. If it does claim such features are supported it might out right skip them or emulate them using an inaccurate but faster approach.