Many thanks to ltn for a workaround solution he shared on qlik-branch.slack.com!
When running the SSE plugins in the same machine as Qlik Sense, make use of the servicedispatcher and services.conf that exists in:
Make a backup copy of this file since it is overwritten when upgrading to a newer Qlik Sense version.
The services specified in that conf file is started in the specified order and if any of the processes is killed it will be started automatically again.
Simply add your plugin services before the engine service (can be directly after Globals). Example:
DisplayName=Sense SSE Python Plugin
DisplayName=Sense SSE R Plugin
In most cases, if engine have had a connection to the SSE plugin, it usually works to restart the plugin without restarting Qlik Sense Engine service (if the plugin has not changed capabilities).
Also have a look at the following page: https://github.com/qlik-oss/sse-r-plugin/blob/master/GetStarted.md#configure-ssetorserve
Here you can for instance specify an Rserve process that SSEtoRserve will start and monitor automatically. Example:
rProcessPathToStart : Default empty (no additional action, SSEtoRserve assumes that Rserve is running already). If you want SSEtoRserve to start any R process during startup then set it to i.e. C:\Program Files\R\R-3.3.3\bin\x64\Rserve.exe or C:\Program Files\Microsoft\R Open\bin\x64\Rterm.exe or C:\Program Files\R\R-3.3.3\bin\x64\Rterm.exe , depending on what you want. If the process dies then SSEtoRserve will try to start it again after ~10 seconds.