Since Windows 2008 that operating system family knows the difference between "real person" accounts and "software service" accounts. For example, "John Doe" is a "real person", while "Jenkins" is a "software service". The benefit (one among some) is that the administrator can provide different security rule sets for people than for services.

It would be great if Jenkins would allow to "Run as Jenkins software service account" (and make it the default) and then simply remotely creates such a software service account called "Jenkins" (so the administrator doesn neither need to do that, nor imagine a fancy password).

As not even the administrator knows the password of that account, this is a security benefit, besides the improved smartness of the slave installation process.