If mewcancraft decides on highlight-selection, they will not only need to toggle inverse mode but to rewrite the text for each option, and then fill in the region around the text with additional Text( or Line(. Design choices must take into account the calculator's limitations. Especially if thr initial choice was arbitrary, there is no sense in using highlighting when a mark would be functionally equivalent, look no uglier, be slightly faster, require 100 fewer bytes, and allow the tool to fit in one program.
First of all, thanks for the feedback, it always helps to have different standpoints when working on an idea.
Second, I agree with what you said in the second part of your reply, but I'm not the kind of person to give up on something rather quickly. If I run into a problem, I see it as a challenge, because I'm convinced that with enough thought every problem has a solution. Also, if I shape an idea in my mind, it involves my very own style, as opposed to that but with a replacement here and there that makes my program less and less what I intended it to look like. So, if I have a highlight-selection in mind, I want to first find all the possible solutions that might or might not work before actually giving up on it. As the old wise men say: Nothing ventured, nothing gained.