Wine can get quite complicated to configure.
It tends to work best when each app has its own isolated wine prefix. This lets you tweak wine settings/params as needed for each app.
This is how I do it for games using Lutris. I have a few games that work best on particular wine versions that won't be able to share the same prefix.
Title made me think of Lutris. I thought Lutris allowed exactly this with a "fancy" launcher UI on top. You have the game you want to run and then it is installed into a per-game WINE prefix.
From my experience, Bottles and Lutris are pretty similar in terms of the overall experience they try to provide. The main difference (at least at the last time I had used each of them) was that Lutris has a lot of flexibility in being able to have third-parties define and publish configs to be usable, whereas Bottles seemed to have more of a "batteries included" approach to having recipes mostly built-in but with the ability to swap out individual pieces manually (e.g. "use this exact distribution of wine, override this DLL with these flags", etc.). I don't recall Lutris having as good support for modifying configs without having to manually modify the JSON recipes, or Bottles having as much support for sharing recipes to be able to automate them rather than manually clicking around in the GUI to make the choices, but it's possible one or both of them has improved in those areas since I last tried them.
Nowadays, I tend to just run pretty much everything through Steam/Proton. I set `Proton-GE` as the default override for all my games, and then "install" things by adding them via the menu for third-party apps in the Steam UI. In the rare cases that I need to tweak something, I use `protontricks` to invoke `winetricks` on the prefix for the game, and things tend to just work after maybe installing 1-2 things at most.