Perhaps interrogating the job.log file may provide some indication of what the issue is. My suspicion would be overheads in the read movie phase.
Note the potential for slow down accessing TIFFs over networked filesystems in general. Motion correction implements a workaround that copies the file into shared memory prior to reading. This does not happen in RBMC. See the response linked below.