Just a major dropped ball on the game design. The engine doesn't handle an activity allowed - this should never happen. Either you fix the engine or you make it impossible to do said action.
That's exactly what I wanted to point out with this video, I am glad not only I have such opinion.
I mainly did this test for two reasons:
1. To check how game design handles such events as interstellar travels (and permits system)
2. To see if the game engine actually tracks and records your long range progress on the 3D representation of the space
As I see it, answers are:
ad.1. Game design doesn't account for such events like crossing half-way between star systems (whether it is geometric or mass influence half-way) - which should trigger new instance generation and switching onto it.
ad.2. This proved to be true. This was actually my second attempt, first one was on the distance of over 7Ly but after around 0.7 Ly game dropped out due to "Server connection error" and when I logged in back, it placed me in correct distance and 3D placement towards a star I was heading to before. Here it can be seen also when I logged out and logged in and was placed almost at same spot.
Actually the point of logging out and logging in at destination was for the purpose of checking if the game will detect that the position is within different system boundary and will generate an instance for me inside this system. Unfortunately this hasn't happened, which I see as a big flow and game breaker in terms of immersion. What good is the sandbox design if it doesn't allow you to play the way you want it.
Thanks for the comment!