The streamlined version is what "screen -d …" does, so it's some kind of standard feature, isnt it?. The only "drawback" I see is that you have to plan ahead to use screen.
When I start long running jobs, I try do start them that way, so I can check on them (and their output in a screen logfile) from anywhere:
screen -L -Logfile "batch-xyzzy-221005a" -S "xyzzy1" bash job.sh
Now I can just check the log with grep or less, or reattach to it if some action is needed.