Knob sending multiple CC #'s of the same value

If I understand what you want correctly, it's very easy to achieve.
I've just tested the following encoder definition (since you mentioned ".tx", I don't have to explain that this is BCL [emoticon:smiley]):

$encoder 1
  .showvalue on
  .mode 1dot/off
  .resolution 96 96 96 96
  .default 0
  .minmax 0 1
  .tx $B0 $00 val $B0 $01 val $B0 $02 val $B0 $03 val $B0 $04 val $B0 $05 val $B0 $06 val $B0 $07 val $B0 $08 val $B0 $09 val $B0 $0A val $B0 $0B val

When I turn this encoder slightly clockwise, three things happen: the bottom left LED in the encoder's ring goes on, the display briefly says "1", and the BCR outputs a sequence of 12 CC messages with value 1 (B0 00 01, B0 01 01 ... B0 0B 01).
Then when I turn the encoder back counter-clockwise, the bottom left LED goes off, the display briefly says "0", and the BCR outputs the corresponding 12 CC messages with value 0.
In the above definition, ".resolution 96 96 96 96" (equivalent to simply ".resolution 96") is in fact the default resolution for all encoders: 96 values per 360 degrees. In my experience, its responsiveness is ideal here: choosing a lower value only makes it more difficult to switch between the two modes.
However, one aspect of this definition is not ideal: when I keep turning clockwise, the BCR keeps outputting the exact same sequence of 12 CC messages (i.e. with value 1) at every next 1/96th of the full circle - this is simply a quirk of the BCR. This is probably not a problem for your drum machine; however, if you want, you could lower the resolution to something like 16 or 8: then you would have to turn a lot further to make the BCR fire another batch of 12 messages; but of couse this would also increase the rotation back to 0...!

So I think it's much better to use a button for this.
For instance:

$button 33
  .showvalue on
  .default 0
  .mode toggle
  .minmax 0 1
  .tx $B0 $00 val $B0 $01 val $B0 $02 val $B0 $03 val $B0 $04 val $B0 $05 val $B0 $06 val $B0 $07 val $B0 $08 val $B0 $09 val $B0 $0A val $B0 $0B val

When I press this button for the first time, its LED goes on, the display briefly says "on", and the BCR outputs the 12 CC messages with value 1.
When I press this button for the second time, its LED goes out, the display briefly says "off", and the BCR outputs the 12 CC messages with value 0.
So this is much cleaner. But of course it depends on how you want to organize the preset whether this is actually the best way: you might need the buttons for other things.

I have also been considering a BCF2000 as well, perhaps this would work better with the faders having actual physical endpoints?

I've tried this:

$fader 1
  .showvalue on
  .motor on
  .override move
  .keyoverride off
  .default 0
  .minmax 0 1
  .tx $B0 $00 val $B0 $01 val $B0 $02 val $B0 $03 val $B0 $04 val $B0 $05 val $B0 $06 val $B0 $07 val $B0 $08 val $B0 $09 val $B0 $0A val $B0 $0B val

But I didn't feel very comfortable with this: the lower half of the fader's range means "0" and the upper half "1", so the effective switch area is around the mid-point. A fader has no LEDs, so the only "permanent" clue to its current state is the position of the fader itself, which is not ideal, particularly in a dark place.

Also note that a BCF is also substantially heavier than a BCR (due to the motors of the faders).
And at least originally the BCF tended to be about 50% more expensive than the BCR - I'm not familiar with their current prices though...

Anyway, my advice would be to go for a BCR rather than a BCF, and to use a button for this type of definition.
Unless of course the BCF's 8 faders are more useful to you than the BCR's 24 extra encoders.

Hope this helps,
   Mark.