[SPIR-V] Incorrect ignoring globallycoherent with buffer device address approach

What is the issue you're encountering?
I'm designing rendering system which will utilize descriptor indexing, mutable descriptor type for sampled, storage images via ResourceDescriptorHeap feature for every buffer.

I have a question about using:

globallycoherent RWStructuredBuffer<uint32_t> buf = ResourceDescriptorHeap ( ... );

Such pattern presents in SPD algorithm for example. So question is: is it possible to rewrite code snippet above to use vk::BufferPointer paradigm. I could not find similar examples in unit-tests and documentation.

Would you kindly help?

Steps to Reproduce (if applicable)
N/A

Environment

• git submodule update --init has been invoked before build
• hctbuild build parameters: -official -rel -x64 -vs2022 -speak-up -no-dxilconv -spirv
• Visual Studio 2022 Community components were up to date.
• Windows 11 Pro (24H2, Build 26100.4351)
• dxc.exe v1.8.2505.10062 executable, commit SHA-1 94abfe972ad839185965f670329bcf33cd7bccbd

Additional info

• The full shader with non-trivial use case which I plan to refactor: listing

Start with the linked exposure.cs.hlsl listing and the SPIR-V build configuration described in the issue; no repository source file or test entry point is named. Investigate how globallycoherent and vk::BufferPointer are handled, then establish whether the rewrite is supported and what test or documentation would demonstrate the result.