It appears that you clicked nearly every button on the screen before taking that image. Unfortunately this means that it scrolled the first errors off screen and the first errors are generally the most important ones. So I would need an screenshot just like this, but without all the button clicking(the added errors don't reveal anything useful) or at least scroll to the top first. Though as I will explain later, that screenshot may not help.
The Debug mod has 2 effects: the terminal that provides error messages, and the uniquely dangerous effect of causing the game to not crash when it should otherwise crash. Specifically it changes the response to errors to fail out of the current code rather than stop the entire program. There are some rare problems where the debug response is more detrimental than the default response, but even so the error messages are more important.
As far as getting better explanations from you, you have already provided some. Previously you only mentioned that you had problems loading the game, which to me means before reaching the main menu but for others it can mean any time until the mansion shows. The fact that you could reach the main menu and use any buttons eliminates a lot of annoying potential problems.
The reason you can't progress the game menus as far with the Debug mod is that your game had an error while setting up the core game data and failed out before finishing, thus the main menu cannot function because it lacks critical data. Prior to the Debug mod, you had the same error but it Godot decided not to crash for it thus allowing it to quietly corrupt part of the data, which was probably needed for the part that it did stop working. The "frozen" game state that you are referring to is actually called a softlock, as the program has not stopped responding it is not frozen. In a softlock you cannot progress but the program is still responding, or in other words it recieves user input and uses CPU time in a normal fashion. The fact that the button presses do not function as normally expected does not mean that it isn't responding.
I need you to list which mods you have installed as well as their versions, because your current problems are almost certainly caused by installing mods that cause conflicts in the game's code. Resolving conflicts between mods so that they work together is tedious work. The screenshot mentioned above will likely identify the point in the code that the conflict occurs, but I could probably tell you where it was just from the list of installed mods. Fixing a program folder with conflicting mods installed is a headache even for skilled programmers. The easiest fix is to extract a new Strive program folder and try to install a difference order or combination of mods. I have looked at the code of most of the mods so I can tell you which of them will likely be compatible.
If you have trouble remembering which mods are installed, the details.ini file in your Strive program folder will have them listed by name but not the versions.