The load order determines the precedence of changes. If you load mod A before mod B, anything that A changes, which B also changes, will show only those shared changes made by B, since it "overwrites" the changes made by A. Any changes that A makes which B doesn't also change are changed to what A wanted, but again, B would have overwritten the shared changes made by A (changes to the same thing), be that a resource, a texture, a skeleton, or a script.
Conversely, had you loaded B before A, the opposite would be true.
Since you're using Vortex, I'd recommend that where possible, you select the Vortex-suggested load order. You'll see something like
IMO, choose the suggested for the least problems.
In some cases, (in my experience, it's not technically rare but very infrequent) , Vortex will be unable to provide a suggestion. That is, there will be no "(suggested)". At that point, you need to refer to the documentation for the mods involved (A and B in my simple example) in the load order contention, to see if there's any info on that contention (ex: Mod author says: "like you should always load A before B if you have B installed too, because otherwise things won't work right"), or failing that, an educated guess. (in around 500 mod installations, I believe I've had to deal with this around ten times in total (perhaps a few more but not many)
As Weissdorn suggested, there are times when you might want to override the suggested load order. In my experience in around 500 mod installations is that this situation is extremely rare, even
less more rare that situations where Vortex doesn't provide a suggested load order. I've done so only two or three times for all these mod installations.