You don’t seem to understand the issue. Regardless of if that is actually the shortest path, the path doesn’t even start at the correct position! The option I selected for the Seeker script is that it should start it the closest point along the clossest line (“Node Connection” for “Start Point Snapping”). Clearly, it doesn’t do that. THAT is the issue.
Plus, if you look at, the video, the wrong path generated clearly isn’t the shortest path. It already was going along the correct path and it was getting closer and closer, and it suddently generated a path that would required some back tracking, therefore making it logically longer then the correct path.