@robnotyou
Thanks
Maybe I am wrong, but I experienced that the WKWebView is not working the same way on the various simulator iOS devices, at least in the default mode, that is without meta tags injection, so you seem to be sure that with the appropriate meta tag injection it works well on each simulated model.
The meta tag injection is necessary also on real devices, so the default WKWebView is tricking,if you do not know that. Default rendering is different from, let's say, the Android WebView.
I did not know that and I had to add the injection code during the review process for the submission to the AppStore. It was just matter of creating a new build in fact.
But I think that the WKWebView on the simulator could have also further differences and quirkness depending on the particular simulated device.
However the simulator is secondary problem here.
I think that the answer to my question is
"Yes it is possible to have a scaled representation of the real HTML rendering on a physical iOS device (in a sort of frame corresponding to the device itself) in a MacOS or iOS app because the WKWebView is able to do so with suitable meta tags",
provided I have a list of the suitable values for those settings.
Am I wrong?
But I further wonder whether those values are easily calculated, or they are already known because they are available in resources like tables of values, ready-made tools, and so on, if they really exist for every device.