TSM4VE - scheduling and tagging at VM granularity

Can we remove the following limitation ?
Customer would like to use TAGGING at VM level, not at FOLDER level, without changing or replanning the whole VMs infrastructures.
He would like to tag & schedule some VM to daily backup, some other (may be in the same folder) to weekly backup.
.
Discussing with JIM SMITH:
"...For now they should be able to use the new 8.1 features for the rest of the VM estate (that is, for all the other vms). Here is what could be suggested:
1-Set-up in the vSphere Web Client (DP for VMware 8.1) a schedule for the vms that reside in the datacenter, hostcluster (which ever level the customer is going to define the schedule) - this is the schedule for the daily backup
2-Select the 40-50 vms that don't need a backup and exclude them from the schedule (this is done in the vSphere Web Client). Note another way to do this is to put them all in a vm folder and exclude the vmfolder.
3-Create a manual schedule (that is, a schedule as it looked like in DP for VMware 7.1 before tagging) to explicitly backup the 40-50 vms on a weekly basis with its own datamover. Again if the vms are all in a vm folder this would be much easier to manage.
You should still open an RFE for this.
Another question for the RFE - instead of having separate schedule for the 40-50 vms what if there was an option that you can set on the vm which said "only take the backup once a week of this vm". So you could imagine setting up a schedule for the entire datacenter that runs daily and individually marking (tagging) the 40-50 vms to only backup once a week - would that be an acceptable approach?
----------------------------------------------------------------------------------------------
IBM Spectrum Protect for Virtual Environments: Data Protection for VMware User's Guide
Tip: You cannot change the schedule at the VM level. Instead, select a parent
object, such as a folder, and assign the schedule to that parent. If the parent object
contains more child objects or child virtual machines than what you intend to
protect, click Yes in the Exclude from backup field on those objects or virtual
machines. The excluded objects or virtual machines are not backed up when the
schedule runs