Utility Session Management - It's Inside the Database in Teradata 13.10! (UPDATED) - comment by geethareddy

As a continuation to my question above....

I just went through your another forum posting (at http://developer.teradata.com/blog/carrie/2012/06/eliminating-unplanned-delays-within-load-utility-jobs) related to my question, and I understood that the main reason to have the separate WD for Utility work is to avoid any unexpected delays with Auxiliary sessions. After going through all the comments and your responses, i put my interpretation in the form of below example to check my understanding with you on best practice recommendation for handling Utility Jobs to avoid delays. Am i missing anything here?

3 workloads something like below will cover highly critical, Medium and Low priority Batch jobs.
1) WD-BatchNoThrtl-- Covers jobs from important batch IDs under BatchSpecialProfile 
ClassfCrit: BatchSpecialProfile + Utility:FL,ML and FE...allKindsOfUtilities; 
Throttle:
WD Throttle: No
Utility Throttle: Yes (limit 30)
System Throttle: No
EvalOrder: 1

2) WD-BatchWthThrtl-- Covers jobs from rest of the non-critical batch IDs under BatchProfile
ClassfCrit: BatchProfile + Utility:FL,ML and FE...allKindsOfUtilities:
Throttle:
WD Throttle: Yes(limit 15)
Utility Throttle: Yes (limit 30)
System Throttle: No
EvalOrder: 2

3) WD-BatchUtilAux- Covers auxiliary sql sessions from both BatchSpecialProfile & BatchProfile
ClassfCrit: BatchSpecialProfile or BatchProfile 
Throttle: 
WD Throttle: No
Utility Throttle: No
System Throttle: No
EvalOrder: 3
 
-- 

Thanks
Geeta.