just a point here - generally queries only time out from the client dropping the connection not as an internal SQL Server operation unless it's a deadlock. If you set a block using a couple of sql queries you'll find they'll tend to sit there until the end of time.

I run a profiler which captures long running queries based upon duration, but you won't really know a query is long running until it's finished.

It's not difficult to query the dmvs to gather what you need either but sorting out waht's blocked and just running may be trickier