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

Carrie, 
just one last question.
From your presentation, i heard one important point that you have emphasized a lot is to have a seperate the utility work in to seperate workloads having classification critieria 'Utility'
For example, assume a PRODUCTION box with 40 workloads, among which 3 workloads (WD-BatchH,BatchM,BatchL) to support loading.
For these 3 WDs, the classification criterion is simple where we just included the concern profiles (and NOT used the Utility as classifc cri). So who ever the users included in those profiles, that particular work fall into cocnern Workload. The most comman work from these Profile users is loading using Utilities and also do some adhoc INS/UPD/DELs.
Ex:
WD-BatchH clssifcn cri: Profile_1;    WD-BatchM classification criterion: Profile_2;     WD-BatchL classification criterion: Profile_3; 
Here my question is, why it is so important to prevent the non-utility work from classifying to the same workload. 
The reason is the utility workload will be mixed up with regular work and it is tough to analyze and report how the load utilities and concern workloads are performing? OR there is any other performance cocnern.