Running on a 4K monitor with 200% scaling, it appears forms and visual components on them are scaled up unnecessarily? The image shows Scripter demo IDE running w/normal size menus etc, form2 at designtime, and form2 at runtime, where components are oversize. Is that WAD?
What do you mean by WAD?
The problem here is that the scripter form is "design-time". When you "run" it, it becomes "runtime".
High-DPI and scaling is already complex enough in both Windows and Delphi (especially). Adding Scripter on top of it makes it a mess and I'm not sure if a solution can be found.
Have you tried changing the tweaking properties like Scaled and PixelsPerInch to see if and how it changes behavior?
With all due respect, just like customers are hoping to eventually see an improvement in Delphi regarding its IDE designer and HighDPI, you are also in a similar situation here as the maker of the Scripter library. 
But I do get it, it's not something I expect a quick fix for. It would have been good to get specific hints on how to improve things on a higher zoom screen.
I loved the suggestion on trying out the Scaled property; here is what happens to my design form when I flip the property, run the project, stop, flip the property, run, stop..
take 1
take 2
take 3
Well, but then Scripter depends on both Delphi and Windows behavior.
Scripter even has to deal with the fact that it's emulating Delphi design-time but at runtime.
Worse, we have to support different Delphi versions, and the High DPI behavior changes over different Delphi versions.
Finally, just like in Delphi, you also have issues when you have the forms being saved in different DPIs, i.e., one user is designing the form in a computer with High DPI, the other doesn't, or one user is using text scaling, the other doesn't, and one form is open in the same computer, the other is open in a different computer. It's a complete mess, actually.