barbaz wrote:NoScript 10.1.1, Firefox 57, new profile
DEFAULT: only "frame", "fetch", "other" checked
TRUSTED: all checked
UNTRUSTED: nothing checked
CUSTOM: I don't think it has a set default. Seems to pick up whatever you last clicked.
Great @barbaz, thanks for the time in testing and sharing this!

If anyone here has something entirely different under those conditions, please do share.
I went to noscript v10.1.1 Firefox 57 > options > whitelist and found a url to change. I switched to DEFAULT and applied those settings you mentioned, restarted and seems to be sticking. UNTRUSTED on mine had multiple items checked excluding "script" - I cleared all of those as you pointed. TRUSTED = all checked. CUSTOM = understood from your comment.
It's a bit interesting or new to me that modifying something within the Noscript > options > whitelist, globally changes every setting for that category (e.g. DEFAULT, TRUSTED, UNTRUSTED). If you're outside the options and do something to wherever your NoScript icon is to let's say, the DEFAULT category on a url, it will change everything there as well and same for CUSTOM without changing the clock toggle.
I'm not sure at what point during the upgrade from the last working NoSript for Firefox 56 to where NoScript v10.1.1 on Firefox 57 "DEFAULT" had everything checked. This could be the reason why many are commenting that things they normally wouldn't see running with NoScript before Firefox 57, are coming through (e.g. like autoplayback of video/audio on news websites that had those streaming feeds like CNN, CBS, Washington Post, New York Times for example - these were good test sites just for the heavy volume of unnecessary urls loaded and to showcase to friends how much is actually happening when you visit one of these mainstream sites and how very few you actually need to make them work).
I was considering to remove Noscript fully and start over on the running default profile, but it appears that it's deeply packaged into your profile folder's prefs.js file and a simple uninstall won't cut it. At least if needed for saved whitelist url's, one could find them in the prefs.js file with a regular text editor or NoScript > options > debug (checked) and copy the whitelist found within.