You could check the boot string in a policy and create a remediation script that downloads the config and sets the boot string.
I want to caveat this heavily that NCM remediation is NOT meant for this type of task IMO. You can do it..... but as with any script it's your own comfort level with it. Outside of this, I will not list other possibilities as I do not feel it's in your best interest to give you ideas that could break your production devices.
Test it in a lab on a single device before you deploy it.