Apps like Discord don't actually launch Discord.exe directly. When we click on the Discord app icon it actually launches Update.exe with a --processStart Discord.exe argument.
It's safe to assume Update.exe updates the app to the latest version and then with the --processStart Discord.exe argument, it finds the latest version of Discord on your system and opens it.
The problem was, that if we simply added one of the installed Discord.exe executables, it was definitely going to be replaced at some point when Discord gets updated. Likewise, if we simply added Update.exe to Hot Loads, that's not the app that stays open or that we interact with.
I added the 'Indicator' field so you can change what child app is actually watched by Hot Loads once the child has been launched.