There are a couple of other things to be aware of when using this method.

The size of your SQLAGENT.OUT file will continue to grow at a much faster rate than it currently does. SQL Agent logs the deletion of every job, even if it was created with the auto-destruct parameter. You may need to purge the SQLAGENT.OUT file regularly. It also makes it much harder to look for actual useful information in the Agent log because you have to filter out all of the delete messages.

We write commercial software, not an in-house proprietary system. In one instance this caused a problem with third-party monitoring software that a customer had installed on their server. One thing that was monitored was long-running Agent jobs. We created the auto generated jobs with a GUID in the name, so the monitoring software added a new entry to its own tables every time one of them exceeded the monitoring software's run-time threshold. There were eventually hundreds of thousands of rows in this table, and because you would only expect to find a few rows in this table it was not carefully indexed. This caused the monitoring software to gradually consume more and more server resources. This lead to even more long-running jobs, which just made the problem grow faster.