Hi PeekCS,
The central part here might be a discussion of problem analysis.
One technique is the binary elimination procedure. Taking half of the influences away. (…here, for example, the impact of the textures). Then render and have a look. If the problem persists, the other half might produce the problem. So, we take half of those out (a quarter by then). With this, we usually get in a few steps a problem location. Of course, it can be a problem that only occurs when all influences work at the same time. However, it will become quickly apparent.
The other is a replacement tactic. To use different textures, with a single color, for example, or none at all. Perhaps we exchange the whole model and start with a sphere, to create this setup.
I think it is fair to say while talking about movie production standards, that the pipeline is tested with simplified objects first. Then with some more complex, project-related setups, before any full production takes place. Along these tests, any of the problem-solving strategies can take place.
UDIM is for nearly two decades in existence, but its integration is undoubtedly very strong in the Foundry collection of applications, thanks to WETA.
Yes, if you need UDIM as a core technology for your workflow, or perhaps PTex, as well as Atlases, you should make a suggestion then.
https://www.maxon.net/en/support-center
If no one asks about this, chances are high that the development resources focus on requests for other features first.
All the best