We haven't experience any negative impact to performance or other services, after making this change. The service was failing sporadically during non-supported hours, so this just ensured continuous activity until support staff could investigate.
We were able to identify the root cause, but the symptoms haven't reoccurred since we implement the newer SR.
Till now we are unable to find the exact cause of the issue. As per the suggestion from Brent we have automated the QDS restart from service properties, which is actually very helpful. But if any Qlik job is running during the restart of QDS, the job is getting failed.
We are trying to get more information on this and will post if we find anything positive.
Just an update. The reason behind the QDS stop in my case was because of some scans which were scheduled for windows maintenance. So, whenever this scan is taking place, our QDS is stopping. Analysis still going on for the correlation between the scan and the QDS stops but as a workaround we have automated the QDS restart from service properties just like what Brent and you have mentioned.