We might finally be getting the right pair of eyes on the issue, update from support this morning: I was able to replicate this behavior on my side as well, therefore I have opened an internal investigation with our Support Product Specialist team to investigate further.