I responded in the other thread regarding CoCoHue; for those interested, the solution, not CoCoHue-specific, is to use "Set Color Temperature" if you have CT or RGBW bulbs and want a color temperature. The underlying issue is that the "Set Color" action in RM and BC will use the "Set Color" command, not "Set Color Temperature," and so will use RGB mode (HSL values) to approximate CTs. This might get you close on some bulbs but will vary a lot across different manufacturers. On a related note, the standard "Set Color" and "Set Color Temperature" commands use numeric values (HSL or Kelvin, respectively), not names, so any named values you see in an app are up to that app to decide what they mean.
Regarding the Button Controller issue, I am not able to replicate the problem on my end. I am able to add (at the end), insert (at any location), and delete (by selection from the list) actions in Rule-Machine-like fashion, as well as delete entire button actions sections (though it should be noted that recreating them without deleting the actions inside them first does restore their actions, from what I can see). But BC and RM are both heavy users of Hubitat's "dynamic" UI features, and a wrong click somewhere might get you stick in an odd state. If you can figure out how to reproduce the issue from the beginning, staff might be able to find a fix.