Update:
We have still not been able to get around the lengthy scan of all the clips of the 2T of the library that lives on our Quantum SAN. One thing that doesn’t make any since is why the Flame does this every time we change a link parameter or director for relinking, or go back to the conform area of the timeline to fix an improper clip. As if it forgets what it just scanned. It has been a struggle. Commercials are not an issue as they don’t have as much material to rescan, so we don’t notice it as much.
Also, we did find an issue with the AAF’s that were crashing things. There were dynamic links to other timelines in the main Premiere project. Resolve can resolve these links with no issue. Flame can’t. So, Flame either crashes at the attempt or just ignored the dynamic links all together and ripples the layer the amount of time the dynamic link was taking up. Resolve see it and you have the option to unencapsulate the underlying clips from the dynamic link. So, if you unencapsulate the dynamic links in Resolve, then output the AAF with CLIPS ONLY REFERENCE TO ORIGINAL MEDIA in the timeline layers, then the AAF will load and not crash the Flame.
Another issue is dissolves. Any dissolve or fade the goes from a gap to the clip or from a color to a clip does not conform correctly in Flame. Flame always starts the dissolve from the clip or up to the end of clip. Resolve and Premiere can have then set to centered at the front or back of clip, but this does not translate correctly in Flame, thus throwing off the timeline by the amount of frames from the gap to center of the dissolve referenced in the Resolve or Premiere project. Over time, it shortes or extends the layer by that total amount of frames over the layer.
Also, a LOT of DJI mp4 are not readable by Flame, so we are converting in Resolve to ProRes flavors that match the DJI compression. Good times. I guess no different than off-line not being able to read ARRIRAW SUP 6.0 LF files but Flame can. 
This info has been shared with Marta and Yann. However, we are still struggling getting Flame to see the clips to remlink to that are easily linked correctly in Resolve. So, now we are manually doing this and it has cost us a week of time. Well, normally we would have that to conform a movie, or more, but this one is a crazy fast turn.
As is life, folks who don’t know expect the world in unrealistic time frames and ever changing media formats and software.
I do really appreciate support and all the help they are throwing at fixing or developing workarounds for these issues. Thanks Support Team!