We do not store this information anywhere (maybe only in the badger cache, if it’s enabled).
We use this information to update a usage but do not store the record itself. So, when you would remove it from the trash, we need to stat it again.
There are reasons why. The database may be corrupted. Very often on unstable setups, which can hang or reboot in any random time.
It also would take a lot of space to track these records, which FS should handle just fine. Especially if it has enough RAM for a metadata. If it’s a limited setup, well, it will suffer. However, it looks more robust than lean only on a database cache (remember the Disk usage discrepancy? thread?).