Okay. And I should have been more clear. Fair enough.
You're very wrong that FFlogs can provide nothing for you. You're entirely wrong that you cannot use them. There is only one thing they cannot provide, which is an easily accessible bank of parses at precisely i360. Its benchmark, however, can still be approximated via trends from 340 to 370 to 380 (yes, the former tiers still exist on FFlogs), as all their lead parses will still equally account for DRK's only buffs since 4.0. You have the appropriate number available to you. Not conveniently, but you have it. And, as I said, you can come up with an even tighter fit estimate by checking your stat weights before drawing the comparison. That's as close an estimate as anyone else can get; crit chance, jump-sync, and compositional factors will often cause more difference than any 10 item levels to perfect play.
Which is why I have to wonder... Why do you need that number? You just mentioned that a "friggen number" is just a "friggen number" without its context. Well, the context has not changed since the earliest-tier parses accessible. The meta has scarcely if at all changed this expansion. DRK balance and raid buff uptime have not changed since, again, the earliest tier lead parses on FFlogs. Rotation, therefore, and all damage-increasing tricks, have not changed. The context is the percentile. Do what they do. Read the context of their raid buffs against their use of Bloodsplitter. Check their TBN usage against their cotank's skill deployment. The number itself does not matter.
You're right; I dismissed certain portions of your post, almost if I hadn't read them. Because you can do the things you claimed impossible, so long as you -- as you yourself suggested -- pay attention to the context. You say FFlogs can't work for you; I can determine then that you're not using them to their fullest.
I wish it was easier. I wish it didn't damn near require FFlogs. But it's possible to do all the things you claim impossible, all because you're comparing numbers alone--or else asking for precision that is simply not possible save across tens of personal and guiding parses each--not their tricks or rotations or synergies that should be guiding you.
In the future, I'll apply bold.
:: Should it be easier to do this analysis? Yes. Should we need an external site for it? No. But for we now we do need it, but it can technically do all those things you're requesting.