There's some great info on the front page.
I have one correction to offer - if you download the "Normal" version of NWjs then you don't need to add --disable-direct-composition to the "chromium-args" properties (the SDK simply does not exist and cannot be summoned in the Normal build by right-clicking or pressing F12 - ref (build flavours)).
I assume you meant "--disable-devtools" and yes, you're right about the normal builds not having devtools at all.
However I would like to keep NW.js starters away from custom builds and let them install the "safe" NW.js builds by Scirra, usually adding the arg "--disable-devtools" should be enough to turn off all those ways to access the devtools (right-click menu's and F12).
On top of that you're still able to open the devtools if you like to, by eventing your own type of behavior like pressing a secret combination of keys.
...and I have a question. When disabling vsync (by adding --disable-gpu-vsync to the "chromium-args" properties) how can I then change the fps that the game is being run at to, say, 144 when my monitor refreshes at 60 Hz? I don't observe any difference to fps with the argument set (solidly 60) and that happens with or without a system minimum framerate being set.
I'm not sure if that is possible, I will look into that and see if there is a way to do that.
I predict that it's not possible because then there wouldn't be a need for THIS feature request. (Please consider leaving a Star.)
Technically we would drop down the frame rate from ~300fps to 144fps, so I guess It's like the thing they want to achieve.