One correction to my post - it is a combination of ROS (the dsr or Ramdisk Operating System) and CFG (the ramdisk configuration program) that make autostart possible.
When you set up a Horizon ramdisk using the CFG program, you can select whether to autostart the MENU program at system powerup. If the option is turned on, the Horizon ROS (DSR) will look for the MENU program and if found, will load and run it automatically. The title screen is bypassed. You can hold a key (I think it is the shift key) during powerup to bypass the autostart, giving the user a way to force a full start via the cartridge.
The CFG and MENU programs are just EA option 5 programs copied to the ramdisk once it is formatted.
So to tie the tipi idea back to how the ramdisk operates, the idea was to add an autostart path.filename to tipicfg. If set, tipi would auto-run the target program at startup/powerup. (to your point, you could initially set this to tipi.tipicfg) An on/off flag would allow for some additional control. Holding SHIFT could disable autostart for that startup, or disable for all subsequent boots until you re-enable it.
I don't know how the cartridge autostarts play into the sequence here.