Just wanted to link to this comment section: https://www.gamingonlinux.com/articles/an-enhanced-version-of-the-fan-made-half-...
As it illustrates this is a pervasive issue with all AMD hardware regardless of Proprietary or Open-Source drivers.
Especially pay attention to the post by YoRHa-2B (The lead-developer of DXVK, Someone unarguably extremely intimate with both D3D11 and Vulkan):
[excerpt]
"running it with validation layers enabled indicates that there are quite a few bugs in the Vulkan render path. Including invalid shaders, invalid image layout transitions, out-of-bounds image copies, all the fun stuff that leads to undefined behaviour. How does this even work on Nvidia?"
So it's not a problem on Project Borealis' side, but an issue on Epics' side. One of Vulkan's primary goals as an API is to provide such strict driver and specification validation that this sort of thing is avoided completely. But as has been a multi-decade trend Nvidia are arbitrarily "defining" undefined-behaviour driver side instead of forcing the developer to fix their broken code client/backend side. This is honestly quite egregious :(