I thought I posted more of this on LinkedIn, but looks like I did not? Or maybe I did, but LinkedIn seems to not allow me to easily find my own posts even. But either way, it took probably another month (if not more) to finally convince Microsoft to get devs on this, we tried rolling back to previous versions of Office, found one where the issue appeared, collected memory dumps, and eventually this was fixed.
