Mofi gave great advice on tracing the startup process above using the Process Monitor from SysInternals (Microsoft).
As far as starting UEStudio 30 times a day... I would never do that. If you need it that often, then you should start it at the beginning of your day (I have a shortcut in my startup folder to start UEStudio with Windows), and leave it open for the entire day, minimizing it when not needed.
Once you have UEStudio open, use uesFastStart, a handy utility written by one of the users here, which will open your files into UEStudio without trying to "start" UEStudio again. If you set explorer to open with uesFastStart instead of UEStudio, then uesFastStart will check to see if UES is already open, then "drop" the files into UES, which is a much faster operation than the way explorer will usually issue an execute command to UES with the file as a parameter.
The first post in the topic will explain how to do it, and it has links to ueFastStart and uesFastStart.
As far as starting UEStudio 30 times a day... I would never do that. If you need it that often, then you should start it at the beginning of your day (I have a shortcut in my startup folder to start UEStudio with Windows), and leave it open for the entire day, minimizing it when not needed.
Once you have UEStudio open, use uesFastStart, a handy utility written by one of the users here, which will open your files into UEStudio without trying to "start" UEStudio again. If you set explorer to open with uesFastStart instead of UEStudio, then uesFastStart will check to see if UES is already open, then "drop" the files into UES, which is a much faster operation than the way explorer will usually issue an execute command to UES with the file as a parameter.
The first post in the topic will explain how to do it, and it has links to ueFastStart and uesFastStart.

