I think the developer of NoScript would probably issue me a reply along similar lines: “This isn’t a NoScript issue because you’ve enabled scripts yet their site is broken”, or something to that effect.
This really feels like a corner case caused by a weird interaction between Discourse, NoScript, and probably something else. Especially due to the fact that this issue does not systematically occur in my Firefox profiles where NoScript is installed. Perhaps an underlying bug could be tracked down if I was provided with some help in tracking down what’s going on?