While we would all love for a single universal interchange format to exist between all applications used in Media & Entertainment, it is most likely a utopia that will never be achieved.
That being said, each vendor as their own internal format optimized for their needs. Then there are the specifications for each vendor and interchange format itself - XML, AAF, etc. All of these are open to interpretation which leads to interop issues.
I find that video + Audio AAF causes the most problems, especially with double system workflows. Many users find that exporting an XML from Premiere to Resolve first, then letting Resolve export an AAF for Media Composer is better than a direct AAF between the two. I have found in the past the CM_Offset is usually audio related.
Also, depending on everyone's support, be it XML or AAF, things are lossy. Meaning not everything is described - once you get beyond cuts, fades, dissolves, supers, motion FX, resize, etc. things get dicey or not supported at all.
I would suggest trying a V only XML out of PPro to Resolve then an AAF there to Media Composer as a start to see what will be successful.