I doubt there's any kind of a set of features that can be turned off to reduce the memory footprint by any significant amount when most of the memory bloat comes from the application running its own instance of Google Chrome.
"Please hire a $100,000/year native developer for each of my three preferred ecosystems" is usually the good intention that paves the road to Electron.