Welcome. Actually your thoughts reflect many users and you can find plenty of posts that prove this.
Some advice for any application
Postpone the quest for optimal setup, plugin hunting, and experimentation for maximum-level productivity, until you get familiar with a good part of the application. Bothering with such things earlier is a waste of time, because you will have to bother all over again later. They can all help with or even multiply your productivity in their own way (so you won’t avoid them), but they are not a priority. The priority is the kernel, which is ready out-of-the-box. If you don’t like the basic experience (at least more than the alternatives), most probably no change will fix that. There will certainly be compromises and some of them will be mitigated by the mentioned quest, but they should be on secondary issues.
Some advice for Logseq
Support is not a black-or-white thing. Logseq’s support is neither absent nor phenomenal. The documentation is scarce, the community is new, but the material is abundant and the community is active. Therefore, should expect a mixed experience.
Concerning the stress among pages, tags etc. I have written this post.
As for the multitude of your needs, I would create a different graph for each need. I would start from the need that I understand better, build something that satisfies me (not something complete), then carry the experience to the next need. That experience is more important than the advice of a third person who can only guess your actual needs (I suspect even more important than articles and videos). It will also help you make less generic questions, which may attract more specific answers (even by yourself).
If you have the luxury of starting blank, it would be ideal (Logseq is compatible enough, but not perfect).
Keep your expectations realistic, and may it all connect for you.