Well, if you read the post two after it, we said: "When we have it, you will be able to enable it independent of engaging the servos.". The first statement was a bit clumsy. What it meant to convey is that a flight director doesn't strictly have anything to do with servos, but we didn't intend to imply a promise that FD would work without the servos installed.
Nonetheless, that statement was from 3 years ago, which was well before we actually had an actual product in the works. In the end, we decided to tie the flight director to the presence of servos upon this release because in our system, the presence of servos is what turns on all of the AP interface, code hooks, etc. So while it's easy to say "just let me turn on the FD even if I don't have servos", realize that there is lots of testing that you have to do to make sure that the behaviors you are after are the behaviors you end up with. We'll keep an eye on this capability for the future, but no promises.