Depending on how the content was ripped, it may make sense to do the export.
If the files were ripped in Sooloos (Control:PC/Control:15), all the metadata will exist in the Sooloos database only. Roon can sometimes do well with just the raw files, but there won’t be any file tags at all, and it can be a bit messy, particularly with shorter albums, EPs, and singles.
If you export, all the metadata in the Sooloos database is written into the file tags, and Roon will generally do better identifying the content.
On the other hand, if the files were ripped elsewhere (like in dBpoweramp, or by a ripping service) and then imported into Sooloos, the files will be tagged and may work fine in Roon. You can try this if you want, but doing the export is a one-time process that will ensure the best possible identification.
We have seen some “drift” with some of the older Sooloos-branded produts, especially the Control:10, and I know at one point Meridian implemented a feature that simply resynced all zones after each track as a workaround-- basically like quickly pressing pause twice, which had a negative effect on gapless playback, but did ensure that things synced up after each track.
We don’t have that feature in Roon, but the rest of the underlying code is the same. With Meridian branded audio devices I would expect this to be pretty tight, and I regularly link two MS200s at home.
We have a lot of Meridian customers, and have not had complaints on this, but we could absolutely look into this if certain models or configurations were getting out of sync.