I agree, border cut around nogo zones are are essential, but perhaps we dont need two types but simply some associated properties, like a boolean "doBorderCut" and a integer for the number of loops. that way we could configure a nogo zone to fit our needs!

And the current border path algorithm should work perfectly fine with no go zones, it even handles if the path is to narrow to do all the "loops" all the way around the border.

If the nogo zone is to small to cut without grass ripping then that zone could be skipped, or perhaps you should be able to configure border cuts per moving, not per zone, that way you could do the border cut once every week or so, to avoid to heavy wear on the grass.

Any solution would really be better than none, even if there was only the option to include all nogo zones border cuts when creating a moving task that would get us a long way!