I know - however thats the logic behind how NLEs operate and flame is incompatible as it can not have multiple scaling operations happen concatenated.
Lets look at this case, you have a HD timeline, and UHD source footage.
In premiere you add it to your timeline and use the button “scale to frame size” so it gets “resized” to HD aka your timrelines res, this is pretty much a resize and then if you push-in further its like have a action pushing in on top of it. The scale values in a XML just ingnore the first scaling part, they only give you the timeline relative scale values.
if you had HD proxys in premiere, still same thing applies, or 12K sources, it doesnt matter.
Now resolve can match any input sizing operation , then scale on the timeline and then scale on exports and all scaling operations are concatenated.
This also means that if we just relative scale everything using input scaling/resize and then have our scale values be relative (bascially resize+action) you can change timeline resolution as you want.
its really a design issue in flame. they missed that whole thing where cameras are shooting different resolution that timeline res , or something..