For a K2 process to compile every activity needs to be connected by lines even if the path that gets that activity initialized isn't through that line. This is even the case if line rules are configured so that the workflow could never get to that activity.
With that said I find that using the GOTO method causes the viewflow to look disconnected since there is no proper connected flow at that point. Sometimes that's fine if its an uncommon exception.
If its something expected you might want to consider using the Expire escalation and build rules around the line so that it would only flow that path to the other activity if an activity expired. That way when the business looks at the viewflow they can easily follow the path that was taken.
Regards,
Tim