Short answer: Yeah, just enabling/disabling might not make them start at the starting point first. ResetAI might fix that...
A patrol path is a bunch of XMarker objects linked together in a chain. When setting up the patrol AI package that works with those, the XMarker reference that you specify as the 'starting point' (by putting it's reference in that dropdown box) will be the one they head to and start using first. If you want them to magically appear when you hire them and start patrolling at the starting XMarker, disable them when you dismiss them. Then when you hire them, move them to that starting XMarker point ( npcREF.MoveTo XmarkerREF 0 0 0 ), then enable them, then call a REF.ResetAI on each one of them... that should make them start the package over like it was new and immediately start at the starting XMarker right in front of them.
If you want to skip enabling/disabling and just have them to travel from wherever they're at and start at the starting point when they each get there, use the terminal script to change the value of a quest variable that you set up, and have that variable value be the condition which enables their patrol package (and disallows their previous package). When they change packages they should head right to the starting point and begin patrolling. Forcing that with a REF.ResetAI after you change the quest variable might be a decent idea, but might not be necessary.