Creating a Duplicate Page in different Site Collection

>>You basically have to hand craft out and script each element of the page<<

Okay, but why is that the case?  The video I referenced goes out of its way to say that "this is the content of the page". It's shown to be a string. Not sure why moving the contents of one property to another is an issue, especially if they are the same type .

>>if you're only doing this for one site collection your probably better off just manually building out the page<<

Sorry but this is EXACTLY the scenario we are trying to *avoid.* It needs to be done in TWO site collections where the pages will be saved as drafts and then manually translated into different languages on site in those countries. They should only have to change the text to the correct language and then hit Publish, not have to completely rebuild the page each time there's a relevant piece of news in that country.

Basically, the localization story for news in "modern" is very incomplete and I am desperately trying to come up with some kind of work around that will convince a paying customer that going the Microsoft-recommended route is worth doing.

>>The site scripting is mainly for site templates and deploying custom solutions and pages <<

Sure, but that's not really relevant -- people have been re-purposing things forever.  Cars are for getting people from one place to another,  but some people race them, some people live in them and some people use them to create works of art. 

So failing the simple property update, is there at least some way to open up the existing page and cycle through it's structure so it can be duplicated in an automated loop, without having to be structured by hand? Like Psuedo code:

obj = pageonecontent

obj2 = newpage()

foreach $element in obj

   obj2.add-element($element)

next

Thanks