Listing all the nodes themselves as hotspots isnt going to be the most efficient way, you never need to go directly to where the node is and doing so would look more bottish and you would consume a lot of time travelling to the locations of nodes that are not spawned. Really you only need to get within 20yds (possibly further if you have a fast connection and nodes show up earlier) so that GB2 detects the node and takes over to go gather it
The way i picture doing it most efficiently from a raw pathing PoV would be to imagine a 20yd sphere around every node, then have the path be calculated as the one that is the shortest distance to touch the sphere of the next 3 nodes ahead, which would give you the hotspot to pass via for the next 1 node. That hotspot would then become the start point to do the same calculation from again. Since doing this would effectively generate a path that is at or occasionally below ground level you would probably want to add a +20-30yd height offset to every point on the path to avoid ground collision
I cant think how you would do this in code however with just a set of coordinates, my math skills really arent that good anymore and there are issues still, if you have a low node, then a high up node, then a low node again and your calculating the points in 3D space then the point to reach to be within 20yds of the high node would likely be calculated to inside whatever hill or high thing the node was ontop of.
If you found a way to calculate an initial raw path in a standalone app, my next suggestion would be to create a plugin that does the same calculation but rather than precalculating the entire route it goes node by node and confirms if each point can be pathed to (and doesnt cause stuck behaviour to kick in) as it goes. Ofc if you reached that stage you wouldnt need a preset list of nodes, you could have a monitor mode that just records the node locations as the player does an initial manual farm of the zone then kicks off its calculation process to work out a path on the fly and then spit out the hotspots as it goes until it reconises that its duplicated a hotspot and gone full circle
edit: I think my ramble might have complicated the issue a little more, but perhaps will give you a starting point for your own ideas
edit2: Also this doesnt really give any ideas on how to order the nodes only the way to calculate the best path between them, i can only think the best way would be show the user the list of nodes and allow them to reorder it, apocs profile editor has a fairly good way of showing points on a map and lines between them so you can visualise the route
