Many of my profiles use a command that runs when the profile loads to set up configuration variables, and in some cases run background commands; Currently it is not straightforward to have that command also run if the profile is included into another profile.
Would it be feasible to have an option, possibly for each included profile individually, to have their "Execute a command each time this profile is loaded" command run when the active profile has loaded?
One question is how to handle startup commands that have "Allow other commands to execute while this one is running" checked; As this would be an optional setting, and users could check (using "{PROFILE}") whether the startup command is running with its own profile as the active one, I would argue special handling may not be required, especially if startup commands are executed in the order by which their profiles are in the "Include Profile Commands" list.