Biab defaults to sending a "GM on" message at startup. That means it automatically puts your SC into GM mode. Those drums you don't like are the GM ones and they can't be edited and you can't access the other non GM drum kits when the unit is in GM mode. Tell Biab to not send the "GM on" message and manually put your SC into Performance mode. This should solve your problem with Biab however, if you use a lot of midi files, be aware most midi files are in GM or SMF format so again, they will put your SC into GM mode and you'll have the same problem with the drums. With midi's you have to edit the midi file itself to remove the "GM on" message and make sure your SC is in Performance mode, not GM mode.
Another possible problem is with GM drum mapping. That is, different parts of the kit are mapped to certain keys according to the GM standard like Bb3 for a kick, Ab4 for the ride cymbal, etc. If you do access a non GM kit in your SC but play a GM midi drum track it may or may not sound right. I don't know if Roland uses the GM mapping for all their kits. Most synth makers don't so you could hear anything like a kick part playing as a triangle bell or whatever. I do know that for all the non GM kits in the SC, you can change that mapping and save as a new kit to get around that problem. It's up to you to decide if it's better to change the midi part itself or change the kit mapping because in Biab you can go into the drum kit window and change the mapping notes there to match your SC kit if you want to do it that way.

As you can see, as soon as you get away from using GM as your default, things get tricky.

Bob

Biab/RB latest build, Win 11 Pro, Ryzen 5 5600 G, 512 Gig SSD, 16 Gigs Ram, Steinberg UR22 MkII, Roland Sonic Cell, Kurzweil PC3, Hammond SK1, Korg PA3XPro, Garritan JABB, Hypercanvas, Sampletank 3, more.