The first tiny image you posted in your opening post was rendering lag (a sign of graphics card overload), the lost frames from your last logfile is lack of network bandwidth. Both are completely different things. Since you completely changed your sources and scenes, you need to work out the issue with the network bandwidth first, then see what issues remain if this is solved.
In general, don't keep multiple game captures hanging around. They are not inactive if the corresponding game isn't started - they are actually active all the time and all scanning for their game to show up. If some of these are configured as "Capture any fullscreen application" in their properties, it's even worse, because all game captures set to capture fullscreen are capturing at the same time if some game switches to fullscreen - if you have 5 sources like this, you're capturing the fullscreen game 5 times, thus 5 times resource consumption.
This will even take place, if you deactivate the source by clicking on the small eye icon! Clicking the eye icon only makes a source not showing up in the preview and the output, but the content is still captured. This is to help streamers: you prepare and hide a source in advance, and if you want to show it, you click on the eye icon and the source shows up instantly, without any loading time.
So to avoid all this, remove all but one game capture source that is configured to capture the current fullscreen game. You can create multiple capture sources, one for each game, if you set them all to "Capture specific window" and explicitly capture its window, but don't add too much of them, because this also requires additional resources.
To divide and organize a larger amount of scenes and to avoid having a large amount of scenes active you never use, use scene collections.
About your bandwidth issue, see
https://obsproject.com/wiki/Dropped-Frames-and-General-Connection-Issues