As a CPRS developer (in private practice, not with the VA), I would say that this is very possible. But possible doesn't mean practical.
It would just need a team of of highly trained software developers to comb through all the business logic that is encoded in the code and accurately translate it to the new platform. I don't know about Electron in detail, but my understanding is that it has an environment similar to one finds when coding for a web browser. If that is true, then the limitations of being single threaded, without a great way to program without callbacks / promises etc will introduce some headaches. CPRS also makes use of windows messaging, such that one part of the code will issue a message, with an expectation that another part of the program will pick up the message later as the Windows loop processes messages.
Furthermore, does Electron have a graphical development environment? I.e. can I view a form and drag a button to the place I want it? Or do I have set this all up via text descriptions? Also, will Electron be around in 20 years? My perception of web technology is that most things are written in a disposable manner, i.e. not intended to be maintained for decades. Cobol will probably outlast Electron, if I were to guess.
I guess my point is that most feel that after one spends all the time and effort to jump to a new development platform, one might as well introduce a new design at the same time. And if one is doing that, then why not change the back end as well? I think that is why the VA is wanting to leave VistA altogether and get to something entirely new, such as Cerner or Epic.
Kevin