It can't hurt to try. At worst, the MDs won't have spare CPU long enough for S@H to start up, check in to the Internet, do some work, report results over the Net, and do another cycle. Which the S@H app might be smart enough to realize, and just never activate from background. I doubt S@H would conflict with the MD processes CPU time enough to noticably affect the MD operations.
Why don't you try it and find out? Then let us know. If it works, then maybe there's a whole extra component that can exploit the LMCE followme features: a pool of distributed CPU cycles available when LMCE knows you're not using a machine, even though it's busy doing something no one can actually consume. Which extra capacity could be used for housekeeping, like rebuilding DB indices, or cleaning up video, or just a huge LMCE team competing in S@H!