Hi @Jamie_Browning,
The memory leak issue has plagued many of our users in the last couple of years but the consistency of replicability has been quite low which is why we continuously revisit the issue. Initially, we had some wins when we tackled the Time Machine lead (discussion here), but unfortunately the issue persisted after we released that build, leading us back on the drawing board.
As for the re-scans, a user has pointed that out too on this Forums thread and this introduced an internal discussion with our team. We see how valuable and efficient it would be to make improvements on this particular behavior.