Hello, we get kind the same behavior in the past. As workaround, we have renamed NSRIM.EXE into NSRIMABC.EXE, and scheduled it with Microsoft scheduler. It guaranteed that the nsrim process is running outside our backup windows and not 12 hours after networker service start.
We have to do this renaming by every networker update.
Hope it will help you.