It doesn't save you much; the same calculations still need to happen to determine which points are going to cross the boundary. So you'd only omit drawing that single line segment, instead of calculating where that last segment would intersect the date line. But for drawing out the route, you can't omit that, since it's a pretty large line that's spanning it. The way I have it, it's the same code which splits the line up. The interesting thing I found in my research was the recommendation in the GeoJSON spec on how to handle it:
https://datatracker.ietf.org/doc/html/rfc7946#section-3.1.9
Anyway - I have something working now that I'm going to push to alpha, if you want to try. Shoot me a message on Discord if you're not in the alpha distro list.