Starting in Teradata 13.10, there is a single delay queue for all throttles. This means that queries delayed by system throttles will reside in the same queue as queries delayed by workload throttles. In earlier releases, delay queues were set up independently by type of throttle, and each workload throttle had its own dedicated queue.
Bringing together all delayed objects into a single queue streamlines the entire throttling experience and makes it easier and more accurate to manage internally. However, as a side-effect, the DelayTime field in DBQL needs a second look. DelayTime takes requires slightly different interpretation in 13.10 than you gave it in earlier releases.