Using non-game making frameworks for making games can be interesting, but it will throw up roadblocks that you don’t need (like your multiple sound issue). People who usually make a game in a non-game framework usually do it for those specific challenges, like remaking Doom in Excel.

IMO if you just want to make a game, I suggest using a made for purpose tool. Try Unreal (my tool of choice), Godot (really good open/free option), or Unity (if you must :P).

It’s usually easier to learn a new tool than fighting against a tool you’re familiar with, it will also open possibilities that you may not have thought of (just don’t go too far, feature creep is a beast).

Engines are tools and you should use the one that suits you best. In the same way that you eat soup with a spoon and not with a fork.

From my own experience, I know that it is difficult to move from your comfort zone, but you must carefully evaluate what you want to do in the future.

Unity and Godot are multipurpose engines and allow you to do many things (3D and also 2D). What you spend today learning to use those engines will be used tomorrow in another project.

You must evaluate if what you gain by learning to use these new engines compensates you in the future.

For example, with Unity or Godot, if you want tomorrow, you can add animations or 3D elements, instead, I understand that this is impossible to do with MAUI (I can't make a deeper comparison, because I don't know that tool).

If you want to port your game to Android and MAUI doesn't allow it, that's another reason to learn a tool that does. But of course, you must evaluate the time that you are going to invest learning the new tool, and that is a process that only depends on you.

In general terms it is always a good idea to learn new technologies instead of clinging to just one.