That's not quite how it works. A discrete (separate, distinct) command isn't a program or macro and doesn't have any memory whatsoever. It's just a command that does the same thing every time, immediately, no matter what the current state of the device is. "Input", for example, isn't discrete. Each press of Input does something different. "InputHDMI2", on the other hand, is discrete. No matter what input the TV is currently on, if you send the InputHDMI2 command, it will immediately go to HDMI2, every time. If the device is already on HDMI2, the command will have no effect. There's no skipping or sending of multiple commands or remembering what the last input was.
What you described is sort of how TVs WITHOUT discrete commands work. If your activity needs to go to input 2, but you were last on input 5, the remote does indeed remember that it needs to start from 5 and send the appropriate number of arrow commands or input commands to arrive back at 2. It must mimic what you would do manually because "discrete" commands that go directly to the desired input don't exist for some devices.
This ability to remember which devices are on or off and which inputs they're on is what I call state tracking. If discrete commands are available, state tracking isn't needed. I try to use discretes whenever possible because state tracking isn't totally reliable. If you ever use a different remote or the buttons on the actually device to change inputs or turn it on and off, you get out of sync with Harmony's state tracking. So the next time you use your Harmony, it will select the wrong inputs or turn devices off that you intended to be on. The same thing happens with HDMI-CEC. In that case devices change inputs and power state on their own depending on how their connected, also throwing off Harmony's tracking. Discrete commands, however, don't rely on any tracking and do the same thing ever time. You can send a power off discrete command ten times in a row, and it will always only turn the device off, never back on, as a power toggle command (not discrete) would.
AFAIK, Harmony's automatic state tracking is a unique feature. I don't use Harmony remotes, so if I need state tracking, I have to program all the logic and saving of states myself. This is why I use discretes instead whenever possible. It's not a big deal to do your own state tracking, but your programming is simpler and more reliable without it.
In the OP's case, his TV most likely has discrete power and input commands available, so none of this tracking stuff comes into play. Even if his TV has no discrete commands, then tracking would come into play and work in most case, with the exceptions noted above.