I have a similar "job killer" task. I used sysjobs, sysjobactivity, and sysjobhistory (all in MSDB) to get the information about currently executing jobs. I also have a table to hold the job name and what point the job should be killed.
The opinions expressed herein are strictly personal and do not necessarily reflect the views or policies of my employer.