Certain (Unicode) Characters in a Filename are not Monitored on a Change, sometimes.
(oh, that's an ugly subject, but...)

Create the following two files, complete name, including the "arrows".
[copy & paste should suffice, for the filename]
[open wordpad, tell it to save, give it the names as below]

▶ TEST.TXT
▶ TEST.TXT2

Search for: test.txt

Both file names appear.

Rename "▶ TEST.TXT2" to "TEST.TXT2".
[do this with a 3rd-party file manager, as the issue is not seen when renamed in Everything or Windows Explorer. Altap Salamander or Multi Commander will do. Salamander will show the arrow as a '?' as it doesn't handle unicode. Multi Commander will display the arrow correctly. In both cases, you are able to rename the file, deleting the arrow.]

Both of the old names appear and the newly renamed TEST.TXT2.

Only "▶ TEST.TXT" & "TEST.TXT2" should show.

Don't know offhand if it's the particular character, or the particular character as the first "letter" in the file name, or ...?

Are these files from a NTFS or folder index?
Can you please check if process explorer shows any open handles to these files?
If the issue is reproducible, could you please post verbose debug output when renaming the files.
This verbose debug output will show the USN journal changes.

[didn't realize you can play it directly. when i went to download it, gave some bs message, "Too many users have viewed or downloaded this file recently". better i'd think if you can download. what a bunch of crap.]

Files names that include non-ascii characters are not purged when renamed using a utility that changes the name by its short file name (SFN).
(Or maybe more generally files that are renamed using a utility that changes the name by its SFN?)

It's the same issue with detecting which hard link was reference from the USN entry.
The USN Journal uses only one hard link filename, usually the first WIN32 filename in the MFT (not the filename that was used in the rename).
Filenames are flaged as WIN32 or DOS, so it's odd that the DOS filename was picked, unless it was flagged as WIN32..

The plan is to look-up all WIN32 filenames in the MFT from the USN entry.
This will allow Everything to use the correct filename and update the date modified / size for all hard links.