Due dates are useless. Time tracking should be estimated amount of work and logged work against that estimate. Consider the two use cases:

Worker has 12 tasks meticulously duedated. Suddenly, someone swoops in asking for a bugfix that takes a day to complete. Now, those 12 due dates need to be adjusted.

Worker has 12 tasks meticulously duedated. Suddenly, one task slated towards the end becomes higher priority. Now, many if not all of the due dates need to be swizzled and rescheduled.
The reality is, the due dates don’t matter at all; all that matters is the worker has 24 days of work scheduled, and that’s what you see on the calendar. The implication is it’s 24 days of work from today; the due date(s) are implied, and the overall due date is the important one. Consider those use cases again:

Worker has 12 tasks timeestimated (24 days total). Suddenly, someone swoops in asking for a bugfix that takes a day to complete. The following day, the worker still has 24 days’ worth of work to do (no adjustments needed).

Worker has 12 tasks timeestimated (24 days total). Suddenly, one task slated towards the end becomes higher priority. The worker logs time into that particular task; time remaining is now 23 days, as it would be otherwise.