You heard correctly, I made the mistake of not associating an email chain with this and that's my mistake.
We are actually in conversation with them about aligning Substance with it, which I've now caught up on and read since the previous post. We're aligning on general export and workflow for Painter mainly right now, but we will be able to work with their team to ensure we've got the proper workflow for the 3ds Max integration with their new shader model while we're doing that.
It does look like it will break compatibility, especially if the legacy node object is not available anymore. So we'll want to address this and have it ready while we're aligning with it on everything else. I do have their shader specification, so we should be able to work with that.
I'm going to work with the demo art team and with the Corona team, to make sure we have a proper representation. Since we'll be redesigning how the workflow works, we can handle imports from our other software and have documentation on how that script works and what it's doing, and to try to match it to explanation of what to do with outputs from our main software. Since you're interested in ensuring that being the case, this would be a natural opportunity to ensure our documentation, workflow script and all are aligned.