Thanks @kve for your suggestions on fixing this one.
Support advised this has been fixed in 2024.2.8 which was released for on-prem 22-Jan-2025. This is confirmed in the Release Notes under PRB0285759.
We’ll upgrade our test environment at some point and verify. We’ve nearly converted the affected Classic configurator to Kinetic in the interim so it may be moot. I’m going to mark this as a Solution and drive on.