To keep up with scooping and last fuel stars we would need the route plotter to recalculate after every jump, this may or may not add unnaceptible delays to buckyballers and other people in a hurry, but if you could disable that route recalculation after each jump it would be ok I suppose.
The issue with this, is that we already know that this could change the plotting or even come up with route not found.
Evidence of this.
Plot a long journey, set out and make a bunch of the jump, quite for the session, comeback the for another play session, and now the game have "forgotten" the already plotted route, so you have to go into galaxy map, and it will now try plot a new route to your target... and depending on where you are and stuff like that, it can now give you no route to target! I still wonder why they do not save the plotted route on your account. So that is recalled and then you can be on your way without having to open the galaxy map first.
Imagine this happening if it would recalculate the route after every jump...
So what we are sort of after is to have the message appears in the correct system, if you have been fuel scooping at every opportunity. So it checks against your current plotted route, how many more jumps you can do and then update when you are jumping to the currently last scoopable star, it can now display that correctly.
This should in theory not cost much performance, as all of this information needed for this should already be on the client, as we have a plotted route and we know the jump range, and how much fuel we have, and what kind of stars there are in the plotted route etc. So in theory this should not need any extra server communication and be entirely done client side.