There are many reasons why the controls are not exposed:
First and foremost there are too many of them (close to a million), secondly loading midi-programs sets internal state, so the plugin modifies its state. Hence they cannot be standard control-ports: If you could set the controls using a GUI and set the controls using midi-CC or midi-programs there'll be a conflict. You can't have both.
setBfree does send feedback (outgoing midi) about the current state. e.g If you load a program, motorized drawbars do follow.
The "desktop" interface of setBfree is quite elaborate (midi bindings, config dialog, program and preset managament). So far nobody volunteered to expose this complexity in a HTML GUI (and I don't think it's currently even possible with the MOD to send messages to/from the GUI).