You should be able to create a rule that blocks the access. I ran a test where I tried to block curl.exe. Just specifying "curl.exe" did not work. I had to include the full path to the program.
On my pc I have an old version of curl in the Utils folder, and the one that comes with Windows in the system32 folder. By just running "curl", windows loads the one from system32 since it finds that one first via the path.
After I ran the first curl (and got the redirect response), I applied the firewall rule to block access. The second test failed to connect (blocked by the firewall).
But explicitly using the version in the utils folder still worked.
If that doesn't work, try looking for DolbyAccess in Application Packages.