I'm still using Winamp 5.x on Win10. It's a comfy thing.
The only issue it gives me is a runtime error 'OK' when I close it; likely one of the plugins causing that.
One day last week, after picking up a Time Life 70's music collection from a garage sale, I popped one in to find CDDB hasn't worked in forever, and FreeDB since 2020. So I did something about it; for the track titles to appear on my wall info-center like my ripped music does from winamp.
The info-center being powered by a raspberry pi 4, I added the CDDB/FreeDB database to it, and pointed the cddb.cddb.com & freedb.freedb.com domains to it (is done with the hosts file, or DNS pointers as I prefer to do). Server & Database obtained from archive.org; I now have the entire database through early 2020 on it, and it won't go away some day!
My Winamp is now using the CD Reader plugin, where you can specify the DB location (server). But in testing, I found that the in_cdda.dll plugin from 2.77 and earlier, uses the CDDBv1/FreeDB protocol too. So specifying or redirecting the hosts to where it's still being openly hosted will work with both, but I went with the stand-alone approach.
It was a trip to see if it could be done, but it can. Even by a novice linux tinkerer like me. The hard, yet awesome part; was getting the 'submissions' system working, so I can add to it should I buy a new album

.
Though, pushing a half century now, the odds of me getting a
new album, are increasingly slim.
In short, you can use the CD Reader plugin to point it to
https://gnudb.gnudb.org, or add a line in your hosts file to point to it and fool your pc into thinking its cddb.com that the winamp <2.78 in_cdda plugin will talk to.
Additionally, other CDDBv1/FreeDB based software (ripping/tagging) will begin to work again as well, doing the latter.
I even tried out putting the winamp 2.77 dll into the plugins folder on 5.666, and it worked. For reference, the latest (CDDBv1) in_cdda.dll version, is v1.71 from Winamp 2.77.