Thanks--it's an interesting question. The beta1 product's scheduling
function was so quirky that it was difficult to describe when it would work
properly.
Given that the OS already contains a well tested scheduling system, why
re-create the wheel in an app which is (nearly) a part of that OS?
I'm not aware of any specific security vulnerabilities in the task
scheduler, but it is frequently-given advice to turn off services that are
not used.
Service Pack 2 did tighten security around the API's used with the task
scheduler.
This service is running by default on all versions of XP and Windows Server
2000 and 2003, but the documentation also states that no system services
depend on it, so I suppose turning it off if you are not using it is an
appropriate choice--but like any other change to the system defaults, you
need to remember that change if some later change to the system doesn't
function as expected.
On my own system, I have no visible scheduled jobs that are not of my own
creation. I do have another hidden scheduled job, like the Windows Defender
job--but it is some form of Microsoft reliablity metric job--probably
something I am running to provide Microsoft with more feedback about how
Windows is used--not a normal part of the OS.
I can see this both ways, and I also suspect that the current design isn't
likely to change. But keep the feedback coming--I know it is getting read.
