Possible bug in function for deleting save-states?

Description

After deleting older save-states, I was unable to load my remaining save-state.

Expected behavior

I should be able to load any remaining save-states, regardless of what was deleted previously.

[What you expected to happen]
I expected to delete save-states 0-18 and leave 19 remaining and playable.

Actual behavior

After deleting save-states 0-18, with 19 remaining, I tried to load save-state 19. Instead, text on-screen indicated: "loading from auto-save SRM" or something like that. Then, I exited the game and re-started. Save-state 19 was gone.

Steps to reproduce the bug

1. Play Pokemon Blue, make many save-states. Also save using the normal Gameboy cartridge save function.
2. Delete older save states, leave the most recent one remaining.
3. Try to launch the most recent save-state.
4. Observe: latest save-state is not launch, instead a much older SRM file is loaded.

Disclaimer, I have not attempted to reproduce this yet. Just describing the sequence of events as I saw it. It's possible this is some kind of user-error but I am quite certain of the sequence of events here.

Bisect Results

Haven't attempted.

Version/Commit

Build: Nov 30 2021
Git RG351MP.aarch64-prerelease-20211130_1728
RetroArch: 1.9.13

I understand my build is somewhat outdated but I didn't see this as a closed or open issue, so I decided to log this issue.

Environment information

Frontend OS: Linux 4.4
GCC 10.3.0 64-bit

The report does not name a source file, test, or entry point. First reproduce the save-state deletion and loading sequence with Pokemon Blue and the stated RetroArch build, then trace the save-state and SRM loading behavior; done means the remaining save-state loads successfully after earlier states are deleted.