Currently, engine evaluates expression with upper limit on DBKEY after some available record is found.
Here, available is: non-deleted and visible to the current transaction.
After mass DELETE there could be a lot of deleted records before one available will be found. I.e. engine could read many more records beyond of upper limit on DBKEY before check is made.
Thus it will be much more effective to check for DBKEY's upper limit more early, before check for record availability.