Path visualizer optimization (Orbit line)

In an offline conversation, @mramato mentioned that orbit lines were not well optimized. I think he was talking about `PathVisualizer` and/or related classes. I searched and couldn't find an issue on this, maybe it's tucked away on a roadmap someplace, but I didn't see it. Close if dup.

@mramato can you explain in more technical detail here what kinds of improvements are needed to get the best performance for scenes with hundreds of orbit lines?

Start by reading PathVisualizer and any related classes to understand how orbit lines are handled. The issue does not identify a specific bottleneck, target behavior, test, or completion criterion; maintainer guidance is needed to define the performance improvements for scenes with hundreds of orbit lines.

Written by the indexing model from the issue text.