I just want to make sure this BaSS is serious and scalable enough to handle massive boolean CRUD operations from my production product.
You're optimizing prematurely. Have you got no faith in your dependencies?
I, too, would like to know the answer to this. If this solution scales, I have a wonderful idea for a service that can store arbitrary data using 8 boolean values per byte.
Imagine all the power that this booleans service has brought to the boolean data type being available for arbitrary data types as well!
How will such a solution store the adress of the byte?
Using an additional byte for the size of the address and the specified number of bytes for the address itself. Then you will only need a few identifiers stored locally to access all the bits.
And now we have a scalable way of updating the answer in the future.