Perhaps "internal label" for the display would be better? Have the display save a set label to its own config and use it if the label is edited.
Eh, that adds a layer of complexity that I don't think is really necessary. The LDB specification allows data objects to specify a "label", a "text", and an "icon" for display purposes. It seems pretty silly to say "okay, this data object specifies that its label is X, but we want to show Y here and Z there". I can't really think of too many reasons why you'd need to show a plugin on more than one display, and can't think of any reasons why you'd need to use a different label for the same plugin on each display. Thus, what you're suggesting is just extra bloat for no real purpose.
Sounds like SBC is indeed stomping the LDB plugins' data, which is bad bad bad.
Not really; all it's doing is changing the LDB object's label attribute. It's the same thing a plugin does when it sets its text or icon attributes; all display addons pick up on the changes. The only difference in this case is that instead of the plugin changing its own label, a display is doing it. Since most plugins are designed to be simple, and do not provide a full-fledged GUI through which something like configuring the label would be feasible, I think it's quite reasonable for a display addon to provide the interface for doing this.
If it helps, my current settings are "show on mouseover" with a 2-second timeout, max bin width 500, max blocks per row 50 (I don't really care how many get shown per row since I'm using the max-width setting, so I just picked a high number).
I've noticed for a while that the bin does not properly resize itself to accomodate plugins whose text length changes greatly. For example, the plugin Junkie shows me the name and vendor sell value of the least valuable item in my inventory. Obviously, this tends to change, and can be anything from "[Bat Fang]" to "[Gargantuan Axe of the Enormous Name]". I have my bin configured to use a maximum width; when the plugin's text is too long to fit on the row, it should get pushed to a new row. However, most of the time, it does not do so, leaving 90% of the plugin's text hanging off the visible bin. This still occurs in the new version you posted.