Well maybe it isn't ideal but there is really only 3 reasons I still use Winamp these days.. one is my medialibrary and second is the chapterlist plugin for cpro and I guess 3rd is cpro single gui type skins, trying to make in something similar to all that winamp in that foobar garbage isn't that easy.... both medialibrary and chapterlist have been in use for many years and have so much data on the music I play that its hard to just move to another media player.
Still I've been thinking starting a pet project using javafx or Unity for a crossplatform media player and just re-implementing chapterlist its such a simple extension but so useful for me, and with the direction Unity is going with supporting low end stuff better on mobile and also the Project Tiny, I dunno maybe just make my own is the way to go..at least I could design the frontend the way I always wanted and I never minded a single gui, winamps detachable windows only ever worked for classic skins and I never really cared for it much as I always wanted the medialibrary and playlist in view (playlist also never bothered supporting tabs an inimproved playlist view like aimp or foobar) and then cPro ext and skins worked so well.. but none of these modern skins for winamp were all that friendly for people to make new skins or customize layout...
maki and xml are just not great anymore to use, bit of dying art doing anything for winamp in terms of skinning or even plugins... so yeah glad Wacup exists it will hold me out for a while, plus I'm on win10 and the official winamp is broken with cpro, but for me I see cross platform (linux/android/ windows) being where I'd rather go and have a media player that works across them all and not having to find some inferior one to use.. I'm still so shocked spotifiy media player is so bloody crap and they get shittons of money.. so adding support for that (ie premium account support can use the api to get complete songs) would also be a thing to do (I believe there is already a unity asset supporting that functionality so it would be a good start) .. not even a fan of electron can't stand javascrap over usage in the industry but the chrome dev inspector works so well and css/html element layouts are something anyone could get into making skins for so that's really the only reason I mentioned it, but yeah it wouldn't be easy to support.