systemd-run is actually very nifty to run programs in a resource controlled mode. It is pretty much a better "isolate" (http://www.ucw.cz/moe/isolate.1.html).

The problem is that systemd-run does not allow programs to be run with resource controls. I am aware of the --slice parameter, but that is an umbrella resource control:  If I run 5 different programs simultaneously (with differing resource requirements), It does not let me allocate resource control on a per run basis. The other solution suggested to me on IRC was to issue a "systemctl set-property" after firing the systemd-run, which really does not serve the purpose.

I tried passing a .service file to systemd-run (which allows specification of resource controls within it), but it doesnt seem to execute it. In fact, I would argue that systemd-run should simply read in a .service file (which has all the --slice and --scope parameters built in), honor the resource controls and execute it. You can ignore the dependencies, etc. which are not required. All the commandline arguments would be unnecessary.