I see that the original thread with Shane is still escalated.
I recognise it, as I was the second tier that worked on the issue originally reported, and I was able to easily reproduce the problem on my own test site, and escalated that to the developers.
Checking the internal tickets I see that the issue has been added to the development board for the next dev cycle. That sprint will be focused on WooCommerce, so it makes sense to look into this issue at the same time.
We are just nearing the end of this dev cycle (plugin updates should be available as early as next week if testing proceeds well), and so work should begin soon on the WooCommerce tickets, including yours.
I'm sorry we don't have a solution for you yet, but we haven't forgotten you.
I think you can close this, as we still have the other thread open.
