I understand the temptation all too well, but I’ve been teaching and training people in a variety of industries in many different applications for 30+ years and everyone always wants to run ahead before they’re ready to. DEVONthink is like Photoshop. They are both deeeeep* applications with many functions available.
I’ve got over 30,000 working hours in DEVONthink and have run Photoshop since 1995, but I still wouldn’t say I’ve mastered either. (@cgrunenberg is the only person on the planet that could rightly make that claim 
) So I know a ton about how to use both but there are things I don’t necessarily use often. And that’s okay, for me as well as you and anyone else.
Use our apps as you need to use them, but leave some time to play and explore occasionally.
Also, there’s no shame in using a system then later changing it. I do most of my support in a DEVONthink database and have since I started almost 11 years ago. I am currently working with a third version of a support database, the first being used for five years, the second for about three. No harm, no foul, no shame in it. Just part of the journey as I evolve my thinking and approach, retaining the parts I constantly use and letting go or varying those I don’t.
And because it’s an excellent vignette of someone working through these things, I will point you back to this excellent post from @IvanPsy …