AFAIK Corel was made aware of the issue back in April, certainly when I had another go at support in Sep/Oct I was told it was a known issue and politely told to drop it.
In my opinion, they can't fix it so don't expect a resolution for this, and if it were
somehow to come it would be as a result of a partial re-write and packaged as X4. Upgrade fee, please.
I'm a developer myself and have previous experience of trying to cajole an ancient (1996) third party component whose developer had long been lost through multiple acquisitions - sound familiar anyone? - into working with modern hardware and operating systems. It was horrendous, and even crazy things like what printer driver the customers used would affect whether this wretched spreadsheet component generated memory leaks or not...
Anyway, it would not surprise me if the Corel coders are finding themselves in a similar situation, where an old underlying code base is throwing up strange compatibility issues with modern hardware and operating systems.
It's not clear how many people it affects - certainly there are a whole bunch of us here that have been hit by it, but there could be many thousands out there that don't experience it, or indeed don't edit images the same way and have therefore not noticed it.
From a commercial stand point the cost/benefit of resolving this by clean-sheeting great chunks of code for a probable minority of users who have reported this is not in our favour...
So, I wouldn't recommend waiting for a resolution - learn to live with it, or migrate to a different solution