The main change on 4.6 is that you first create the task and then assign (schedule) them.
For example, for On Demand Scan for VSE, you create the task telling what to scan, heuristic level, etc. And then assign it.
So you may have a single task with multiple assigns.
Regarding the assignment, you can still break the inheritance and schedule the task to run in another time for that system or group.
Regarding the task itself, you'll need to create another task to assign for that system, it's not possible to change that just for one system or group.
In my opinion, this feature is really useful, because it's more likely that you have to change the schedule than change the task properties.
Hope that helps.
Thanks for your response. I'm on the other side of the fence. Schedule time doesn't need to be changed but what is being deployed does.