Nope- different processor and a different SDK which means a different set of possible 'bugs', each of vwhich will need to be handled differently to make things right.
As Nigel said, Viofo can't do any more till they update the SDK so how about harping to them on their site instead and see whether that does you any good either. Nobody like waiting but when there is nothing else you can do that's what you do. And you've been given a stop-gap fix to address this issue until that new SDK comes out which is better service than 90%+ of the cam manufacturers would do for you.
Phil
I'm not harping on Viofo. Matter of fact, I gave him specific details on how to replicate the problem vs. 1.11 Firmware. So that this information can be passed along. It isn't Bill Zhou's fault. He is relegated to handing this information over to those responsible for releasing an SDK with a fix.
Now that he's explained where the issue arose.
As far as the SDK goes for the 4K 129, if the bug isn't discovered in the A129 Duo, then it could be replicated by mistake in later SDK's for other products. Because the exact reason of frame duplication hasn't been identified.
It's like saying You have Windows 7 and Windows 10. Just because windows 10 is a whole new platform, doesn't mean exploits, bugs, etc aren't carried over. While the 4k A129 uses different hardware and a different SDK, we don't know what caused the issue on the A129 Duo, so how can you confidently say it won't reappear?