Glad it works, and thanks for testing the build and reporting back.
On the exclusion question: there is a reason it worked without you adding anything, and it is worth knowing before you ever need to. The plugin already tags every script it enqueues with the opt-out attributes the major optimisers honour: data-no-defer, data-no-optimize, data-no-minify, data-cfasync=”false” and data-ao-skip. That is deliberate rather than incidental, because a deferred or delayed consent banner defeats the point of the plugin. The banner and the interceptor that blocks third-party trackers before consent have to run at page load, not at the first click, otherwise the trackers released by that same click get to run alongside the banner.
If “Remove unused JS” ever does strip something anyway, exclude the directory rather than a filename:
/wp-content/plugins/faz-cookie-manager/frontend/js/
That covers every bundle at once. On a default install only two of them load, script.min.js and a11y.min.js, but gcm.min.js, tcf-cmp.min.js, wca.min.js and microsoft-consent.min.js appear as soon as the matching feature is on (Google Consent Mode, IAB TCF, WP Consent API, Microsoft UET and Clarity), and a path exclusion keeps working when you turn one of those on later. There is also a second reason: with WP_DEBUG or SCRIPT_DEBUG on, the plugin serves script.js instead of script.min.js, so an exclusion written against the minified name would quietly stop matching.
There is one more path worth excluding together with it:
/wp-content/uploads/faz-cookie-manager/assets/
That directory holds a small generated file, config-.js, which carries the provider blocking patterns and the cookie category map. It is separate from the main bundle so your visitors’ browsers can cache it instead of receiving it inside every page. The main bundle merges it back before it runs, so if that file is removed the bundle loses the patterns it blocks with. Note the hash in the name: it is computed from the contents, so the filename changes whenever your cookie or category configuration changes. Excluding it by its current exact filename would work today and silently stop working the next time you edit a category, which is exactly the kind of failure nobody notices.
One case where none of this applies: if you turn on “Ad-blocker compatibility mode” in Banner Control, the bundles stop being separate files and are inlined into the page, so there is nothing left to exclude.
