Qubes doesn’t tend to be about consolidating things onto fewer virtual machines. It’s usually about “compartmentalizing.”
In fact, it can get very extreme on compartmentalizing. There are people here who literally install one application per template, so that they end up with a menu that lists applications (but each one is in its own VM). That does mean they do a lot of copying and pasting between VMs, but that’s not bad at all. I’m fairly new to this and I don’t think I’ll go quite that far [but then again, who knows?], but I did just split a VM I own into two, one with stuff to develop software on it, the other to look at things, process photographs, and write documents on. The two activities never cross over, so there was no reason to keep them together (and oftentimes, the less stuff on a VM, the faster it boots). That latter VM still seems like a bit of a grab bag of things, so I will probably break it up at some point, as well.
I did do a lot of planning to try to ensure I wouldn’t ever install the same piece of software twice (and I got to the point where there was exactly one case of doing it twice, but it was something very small); perhaps that’s what you mean by “consolidation.” If, for existence you often use a draw program with a word processor, and also often use it with a powerpoint like program, but you never use the word processor and the powerpoint program together, you could: 1) clone a template, call it A, 2) install the draw program on A. 3) clone A to B. 4) install the word processor on A, and then 4) install the powerpoint-like program on B. You’ve installed each program once, but have two different VMs. That keeps your powerpoint and wordprocessor activities separate, but lets you consolidate a little (and without redundant installs).
I’ll make one more suggestion: Keep a clean copy of your Fedora template somewhere, so you can always base new VMs off of it, rather than the last thing you did.
That should work with Nextcloud as well…