Yes, that's absolutely doable! I even do it myself to fix the terrible latency that one of my capture cards has by default.
Use the "Get current settings" button to get both the wrong and right settings, and then trim it manually to only keep the part that changed. It may not hurt to keep all of it, but I've seen and even designed side-effects on purpose, even when writing the same value, so I try to avoid that when I can.
This is also one of the very few times I'll use a Wait action, and you'll notice it's very short. Normally, I use a different macro for each step in a sequence, and use the condition timers instead. This one is all in one macro because it's "atomic", as programmers call it: can't (or shouldn't) be broken down any further or interrupted, for any reason at all, not even pedantically.
The (*) after the name, in my naming convention, means that it has a docked button. Click the gear icon at the top-right, then:
