Clarify what you mean by "Scheduler".

LUCI Scheduler (which will replace Buildbot scheduler) has this feature already (https://screenshot.googleplex.com/VdqDdFQoH8m.png this is https://luci-scheduler.appspot.com/jobs/infra/infra-continuous-trusty-64)

But LUCI Scheduler is not generally available yet, so I assume you are asking about some other scheduler?

Oh, awesome, I didn't know about that -- that's exactly what I had in mind. So, our use-case in  bug 705561  could solved at some point after starting to use the LUCI scheduler?

Is there anything we could do to try it out early for running wpt import/export jobs?

In theory there's a way to start using it now, but it lacks some functionality:
1. No emails or any other notifications about redness.
2. "Pause" button (and other buttons in UI) is currently accessible only to mdb/chrome-troopers.

We'll also need to setup a (small) dedicated Swarming bot pool just for WPT jobs, since  these jobs need commit access, and there's no good way to run such jobs on general Chrome pool of bots currently.

If you decide to try it, the rough plan would be:
1. Setup a new "pool:ChromeWPT" Swarming pool with 1-2 preallocated bots (swarm*-c1 or something, e.g https://chrome-internal.googlesource.com/infradata/config/+/master/configs/chromium-swarm/bots.cfg#413). 
2. Add "pool:ChromeWPT" ACL that restricts only luci-scheduler@appspot.gserviceaccount.com to post tasks to this pool (e.g https://chrome-internal.googlesource.com/infradata/config/+/master/configs/chromium-swarm-dev/settings.cfg#31 where usable_by points to a chrome-infra-auth.appspot.com group).
3. Configure Puppet to deploy necessary credentials to these bots.
4. Setup cr-buildbucket.cfg and luci-scheduler.cfg configs.

IMHO, it is a bit premature to do it now...

That makes sense. Thanks!