Hey comicomicmars376871,
Generally, yes, it's possible to turn Wurst features into standalone mods. However, doing so takes a lot more than I think most people realize, precisely because you don't have Wurst's GUI, settings, keybinds, and other utilities to work with. There is no script to run that will do it for you, if that's what you were asking about. It's more like you're writing a new mod from scratch.
As for how to do it, well, you basically set up a new Fabric/NeoForge project, add in the code from the Wurst feature you're porting, and through trial and error you'll eventually figure out a way to make it work in that environment. Features that don't need settings are a lot easier to port than the features that do. What I did for the ChestESP mod is to rewrite all of the settings to use Cloth Config instead of Wurst's system. That won't always work, because Wurst has some setting types that don't exist in Cloth Config and vice versa. I have no idea how I would port AutoLibrarian with its custom book offers setting, maybe with a custom fork of Cloth Config or something like that. (What I did for WI Zoom is to just ignore the settings completely and now reviews of the mod say they like the simplicity, LOL.)
And about Wurst supporting newer Minecraft versions than NoFog mods, that's probably the biggest unsolved problem with standalone mods: Someone has to keep them all updated separately with new Minecraft versions. It's so much easier when you just have one big mod to update. I have a semi-automated workflow for updating WI Zoom and Mo Glass, but as it stands right now that would absolutely not scale to the 200-ish mods required to make every Wurst feature standalone. I think Mcjty holds the current world record for most Minecraft mods actively maintained by one person, and that's only about 40 mods. I don't think he does snapshots either.
As for altering the list of features in Wurst, that's probably a much easier option if you're just looking to remove some things and don't mind keeping essentials like the GUI. The TooManyHax feature was originally meant to do this for you, but after various issues and compromises it just kind of disables features now instead of removing them. But if you're looking to delete some features from the code, look out for TooManyHax's @DontBlock annotation. It marks features that would break stuff if you removed them.
Hope this helps!
