patches VS dwm-single-tagset-6.2

I am trying to setup my workspaces for stumpwm, but am running into a wall due to not being able to find much documentation, is there is even support, for a few things I want to do. For some background, I am coming from dwm which I have used for a few years and even forked a few times. In dwm I had a rather simple, but extremely useful, setup where I would store specific types of programs on specific tags. I was able to figure out getting this done in stumpwm and it working just fine. The main issue with this portion of my workspace setup is that the Default workspace still exists. I have tried to figure out how to delete it, but cannot. I know how to rename it, so I could just do that and use it for my terminals, but the issue arises where I have no idea how to change it from the default stacking layout to the dynamic one. Any advice? Additionally, is there a way to get something like dwm's fakefullscreen?

I would like to add the statuscmd (for dwmblocks) feature to my dwm build. I tried this patch (from the suckless website) and this one, from u/bakkeby's Github, which seems more pertinent to my case since I use dwmblocks. I also patched my dwmblocks build with this patch, from the suckless website.

dragcfact is a patch that depends on another patch, cfacts, that assigns a 'weight' to each client in the view area and allows you to resize them by increasing or decreasing the weight of a given client. Yes, in the case of the tile layout that does allow for 'vertical' resizing.

Another way you could achieve this is via floatpos. One way I use this is to toggle tiled windows to become floating and take up 80% of the screen, which gives a kind of semi-fullscreen mode which is kind of nice.

I don't know what they are refering to, but the swallowing that has become popularized is not what that screenshot shows. The functionality is taken from Plan9's window manager, rio. When you launch, say, firefox from a terminal on non-swallowing window managers the terminal just sits there and the window is spawned on it's own. With swallowing, the terminal swallows the window in that the newly spawn windows takes up the window that is the terminal until it exists at which point the terminal window is restored. I can not an example of this in video, but there are patches to implement this into dwm such as rio draw/swallow

dwm-desktop_icons-6.2.diff - hardcoded to not manage windows that have the window type of _NET_WM_WINDOW_TYPE_DESKTOP, for programs that provide desktop icons as an example, and

I'm not really knowledgeable with dwm but googling around I found this thread where someone linked this GitHub repo, which aims to combine different fullscreen patches so they can work together.

I've applied the barmodules patch with the hope of controlling multiple status segments via IPC.

I've switched from i3 to dwm couple days ago. I like it so far but I have one major problem: I can't come up with a comfortable workflow with my dual-monitor setup. I love the way i3 manages multi-monitor setups - single set of workspaces for all monitors, but each workspace is assigned to a monitor. I used it this way for working: Firefox on ws1, Spotify, Slack and Telegram on ws2, terminal running tmux in ws3 (where most of the stuff is done). I keep terminal workspace on the primary monitor and workspaces 1,2 on the secondary monitor - this way I can switch between my messengers and browser without having to hide my code from primary monitor. I really got used to this workflow. Now I'm trying to adapt this sort of workflow to the DWM's philosophy and probably make it better (or at least not worse). I've tried to apply single tagset patch but it has a bug which basically makes it unusable. I really want to try it out and even think of trying to fix it myself since I have some C knowledge and programming background. At this point, I don't really like the fact that I have to press mod + >/< to switch between my monitors, when on i3 I could do it by just focusing the desired workspace. Or maybe I'm just not getting the idea behind separate tags on multiple monitors? I'm sure there's a reason why it works this way. Any advice appreciated.