That's 5. Not 2.
I'm not understanding something. Because I thought if I searched for them by their real name that would see past/through any name I gave them.
If you searched for 'file' you would find them all as that is the underlying node type.
In 2.1.0 we added palette labels to the file/file in nodes so they get labelled as 'Read File' and 'Write File' in the UI to help users distinguish between them.
However, as you have just identified, the search functionality doesn't take the palette label property into account.
But searching only for file opens a big can of worms on the machine.
If I am looking for the node that writes to files, a specific name would help.
But anyway..... Seems that mistake I just mentioned was (luckily for me) a one off.
I have (since) found a heap more of that node and they are all correctly connected to a function node that builds the message correctly for setting the file name.