In ExeOutput 2018, EXE starts slower because the Chromium engine is fat. We must first unpack all required resources. It will be the same in HTMLEXE 2018 if you decide to merge the runtime module files into the EXE.
We hope so. We’re still studying the legality of this.
Not sure what to answer. Each time we give an estimated date, we’re unable to achieve that. Like someone said, “soon”. Anyway, it will be in the beginning of 2018.