I think it's safe to say that without any updates from the devs, despite being provided steps to reproduce the issue above, the community no longer wishes to expend any more effort providing information that goes unused.
It's proven incredibly hard to reproduce and find the root cause of the issue, even with the incredibly helpful and vast amount of material that has been sent to us. We're still working behind the scenes. I am sorry you feel this way. π
I appreciate everything you have done to help us with this issue, I'll continue to push the issue to the team behind the scenes and cross my fingers we find the exact conditions under which this bug exists and eradicate it swiftly. π