I don't think you could introduce multiple Love/Ban fields due to the functionality of the 'ban' setting:
When a track is 'banned' it is prevented from being selected for auto-playlists and is prevented from being played in many situations. If you had two Love/Ban fields, a single track could be both 'loved' and 'banned'.
(It would be unfair to ask MusicBee to decide and hence take sides in a domestic dispute of whether a track should be played or not.

)
A clickable Boolean type field sounds a little more interesting, especially if you could define the yes/no characters or strings to be displayed.
(Having said that, I will note that the <Ticked> field is already available, albeit somewhat visually unappealing, and I have never used this.)