Code Integrity (Memory Integrity/HVCI) blocks an MSIX app's own bundled DLL (vk_swiftshader.dll) - permanent fix beyond reinstalling?

On a machine with Memory Integrity (HVCI) enabled, I've seen Code Integrity reject an MSIX-packaged app's own bundled DLL (vk_swiftshader.dll, a software renderer shipped inside the app itself) at launch - the Code Integrity operational log shows Event 3033, and the app's GPU/renderer process crashes immediately. The package status then shows Modified, NeedsRemediation in Get-AppxPackage, and the app can't relaunch until it's reinstalled.

A reinstall clears the immediate crash but doesn't address the root cause, and the same thing can recur. Is there a documented, permanent remediation for Code Integrity rejecting a Microsoft-signed app's own bundled native DLL under HVCI - e.g. re-signing guidance, a policy exclusion path, or confirmation that this is something app developers need to fix on their end (matching their binary's signing level to what Smart App Control/HVCI requires) rather than something fixable from the Windows side alone?