No, No, No. Sorry.
Age old problems and little help from Rootsmagic over the years.
The problem with outsourcing a solution is that you would have to clealy define exactly what you want.
If I were tackling this problem I would combine everything into one NEW reference database and firstly run all Rootsmagics Auto Merges (check the file properties before and after), I would then work to make events, repositories exactly the same in all respects and then try an Export to Gedcom followed by an Import into another NEW file of a different name and see what Rootsmagic cleans up.
Cleaning the Place List is one important area as any slight differences even in punctuation will result in duplication.
I noticed some missing partners on my database recently and knew they were somewhere, I decided to combine all the gedcom files and split RM databases I have received over the years into one file. The combined file had more 1.3 million individuals and I ran all automatic merges (I trust this process) It was running on my laptop (disconnected from the internet so Microsoft couldn't disturb it with an update) and the process took 9 days to complete. The result was a file with 156K individuals which I keep to the side for reference and dragging and dropping, the file has loads of event and place duplication but if I find a missing spouse which I feen should be there I know it will that combined reference file.