For the Invoke Process activity, the execution will occur on the same machine with no tracks of it in Orchestrator.
As such, the Run Job activity is closer to the Start Job activity because it allows you to interact with the Orchestrator API and trigger your jobs via Orchestrator. It simply bridges the gap between the two by now also allowing you to run your Orchestrator jobs with outputs and with persistence (in an easier way).