Given that I don't know if you used the manifest trick or not, and that the update to 6.5.22.0 will have replaced any renamed manifest with the defaults... (if so, you'd need to swap the names round again)
But OnInsert relies on the main program being loaded, yes. There's no alternative (otherwise there's nothing running to request notification of Insert by Windows, then figure out which drive it was when an insert happens, whether that drive should trigger anything, and if so, what?)
You could maybe insert it then double-click a shortcut to a profile (you can drag a profile or group to the desktop to create one) to manually start things. But if the copy of Pro that launches to run the embedded profile (and then close again) has the default elevated manifest in place, it will then trigger UAC. If the UAC prompt frightens your user, you'll need to play the manifest trick (or create a non-elevated copy of Pro) as described in the KB article. In which case you can presumably go back to Start With Windows anyway...because setting the Scheduled Task not to run with highest privileges won't be conflicting with a manifest file that says it should.
But OnInsert relies on the main program being loaded, yes. There's no alternative (otherwise there's nothing running to request notification of Insert by Windows, then figure out which drive it was when an insert happens, whether that drive should trigger anything, and if so, what?)
You could maybe insert it then double-click a shortcut to a profile (you can drag a profile or group to the desktop to create one) to manually start things. But if the copy of Pro that launches to run the embedded profile (and then close again) has the default elevated manifest in place, it will then trigger UAC. If the UAC prompt frightens your user, you'll need to play the manifest trick (or create a non-elevated copy of Pro) as described in the KB article. In which case you can presumably go back to Start With Windows anyway...because setting the Scheduled Task not to run with highest privileges won't be conflicting with a manifest file that says it should.