Cat5 is good enough for 100m and 100Base-TX and even more. But 100m is the standard and Cat5 is specified for that. For 1000Base-T Cat5e is specified and 100m have to work with it.
Though the 5 and 5e standard differ only in some additional measurement and most of the time the cable is/ was exactly the same. There is absolutely no reason to promote Cat6x or even higher if you do not use 10Gbit or more.
I do extensive networking. Cat6 is needed if the wires are in plenum (ceilings) and pass by interference from other electrical wires. Cat5(e) is not as well shielded and will cause some NICs to start to fail. Otherwise Cat5e will work for 1000m.
I just ran a speed test using 25mb fiber on my ArcaOS side and 5mb fiber on a Linux side.
These crossed the internet for Verizon FIOS to Sprint Business internet. (The Sprint side has an OC48 fiber connection at the Linux side building).
From the Linux side I used ftp and did a get:
150 Opening Binary mode data connection for /efs098va04.tar (20951040 bytes).
226 Binary transfer complete.
20951040 bytes received in 00:42 (479.40 KB/s)
Fromthe Linux side I did an ftp put (To an FTP server I wrote in Java):
mput efs098va04.tar [anpqy?]? y
229 Extended Passive Mode Entered (|||65102|)
150 Opening Binary mode data connection for /tmp/efs098va04.tar.
100% |*************************************| 20460 KB 605.22 KB/s 00:00 ETA
226 Binary transfer complete.
20951040 bytes sent in 00:33 (602.53 KB/s)
Note the speed seems to be limited only by the Sprint speed.
I then tested locally between Windows 10 and ArcaOS between two local subnets using a Netgear router in the middle.
I sent a file from the Windows 10 machine which was not in passive mode:
200 Type set to I.
ftp> put seim_winvmf.exe
200 PORT command successful.
150 Opening Binary mode data connection for /tmp/seim_winvmf.exe.
226 Binary transfer complete.
ftp: 45924170 bytes sent in 6.18Seconds 7425.09Kbytes/sec.
Looks like the speed is fine.