It slightly modifies the model of allocation, true - but it does it within the same locality preference.
I was specifically targetting multiple cores which are free in a executor and there are tasks which can be PROCESS_LOCAL or NODE_LOCAL on that worker; but were not getting scheduled as that due to the earlier model.
The implication on RACK_LOCAL and ANY is interesting, and is an unintended side-effect of this changed allocation model.