As the title says, it would be nice if I didn't have to bundle Mod Menu as a dependency just to show the configuration menu while not really using other features.

The main reason why I mention this is because I typically don't like adding libraries to my mods if they aren't really used by the mod itself as that only creates unwanted dependencies.

My thought so far is to use the same way as one would do when wanting to add a config screen but instead of using ModMenuApi as the implementing interface, one can use Function<Screen, Screen> (or UnaryOperator<Screen>) where the first Screen type represents the previous screen and the second Screen represents the "config" screen. Instead of using getModConfigScreenFactory(), apply(Screen) is used instead.

Are you wanting to get rid of Mod Menu as a compile-time dependency? Mod Menu does not need to be a runtime dependency or bundled because the entrypoint will only be called when Mod Menu is installed.