I found out the reason why it was being such a naughty little girl for quite some time. It was all due to my own stupidity, but what it's doing now just makes no fucking sense at all.

I had told it to do local tests only. In Amavisd terms, anything related to connecting to remote servers and performing 3rd party scanning had been disabled for more moons than I'm willing to mention. That was an easy fix, plus finally realizing that the home-dir of the 'user' running the program had been incorrect for AGES. I honestly don't even know how the damn thing was working for all this time.

The issue now is that when I run Amavisd in debug mode and keep it to the foreground, it works fucking fantastic and tags messages with scores in the 30's. However, if I run the same program in the background and not in debug mode, it goes back to acting all bitchy and tagging messages with scores of 4.9 where the same message got a 32.9 in debug mode.

For now, I'm gonna keep it in the foreground because I've put too much effort into it already today... but I will eventually find the solution to this biznitch!!

addendum

I didn't do anything other than try again and it seems to be working now.
One Postfix upgrade later and this thing is working GRRRRRRRRRRRREAT!!!

Even Razor2, Pyzor AND DCC are all working in unison.