Probably, a caching of the system info for the last connection would be a better solution, but I agree with the current approach for the "keep nodes online as much as possible" option.

I suppose that for other modes the behavior may become misleading. AFAIK, Jenkins reconnects the node to run tasks on it (including the system info retrieval?)