TL;DR - For your case, go ahead and set it to manual if you like.  You can disable it if you aren't using SmartLock.  It's there to handle a race condition that can occur when changing certain parameters on a worm domain, which you obviously would not need.  As far as it affecting other jobs, in general, you won't notice.  It chews up a spot in the job engine run queue when running, but it doesn't belong to an exclusion group so other than being one of the 3 jobs that can run at a time, it doesn't hurt anyone.  It's priority is pretty low (6) so it will yield to more critical jobs if the job run queue fills.  SnapDelete, for example, has a priority of 2 so it will take precedence over WormQueue.      SyncIQ runs outside of the job engine, so there's no effect there. 
Hello All,  we have Worm queue job running everyday at 10:00 pm on all clusters, we dont use Smartlock feature, Smartlock license is inactive as well, can i go ahead and disable WormQueue job, we have syncIQ jobs running everyday, does this affect SyncIQ or Snapshot?  -Thanks Pradeep
WormQueue can it be disabled