RTC-SCM-CLI: lscm.bat launches second instance of scm.exe in case of error

I'm using RTC CLI tool from the package: RTC-scmTools-Win-4.0.3

I executed below steps:

1. Opened command prompt and executed "help" command using lscm.bat

• As this is the first time lscm.bat is called in my PC, it took some additional time and it launched scm.exe => fine
  
• help information is displayed properly.
  

2. In the same command prompt, executed "load" command using lscm.bat (without any login)

• load command failed with error: Failed to acquire locks on requested sandboxes in 60000ms

3. In the same command prompt,executed "login" command using lscm.bat (As I've not logged in before, I thought that was the reason why the previous "load" command failed)

• It took additional time before giving the status as "login successful"
• When I looked in Task Manager, another instance of scm.exe was running

4. When I executed "load" command again, it was successful this time. But I think this command was executed by the second instance of scm.exe and the first instance of scm.exe is sitting there idle. (But I'm not sure)

Quesion:
In step-3, why another instance of scm.exe is started in case of the "load" command failure ?
It affects the performance, as the user has to bear with the start up time of second instance of scm.exe and also more resource consumption as the first instance of scm.exe is still running in task manager.
Also, I'm not sure whether this behavior happens every time an error occurs in CLI. Could you please clarify ?

Thanks in advance.