Conflicting Process - App defaults not respected when Windows Default template exists

If a Windows Default template exists, the Conflicting Process behavior from that template is applied to all future deployments - even when the template has not changed this setting from its default value. Because the template’s values take precedence over the application’s own defaults, apps like Google Chrome, which normally default to “Perform the installation”, instead inherit the template’s behavior.

This results in all deployments prompting the user to close the application, even when most apps do not require user notification.

It would be beneficial if deployments could instead fall back to the application’s native default Conflicting Process behavior whenever the app is compatible with “Perform the installation,” rather than requiring manual validation using the guidance at:
https://patchmypc.com/kb/manage-conflicting-processes-when-updating/#h-when-to-enable-notify-the-user-to-close-the-application

My intent is to use templates for things like Assignments (e.g., All Users – Available, All Users – Update Only), removing desktop shortcuts, and enabling “Allow Available Uninstall.” However, this currently cannot be done without unintentionally overriding each application’s built‑in Conflicting Process default.