Looks like you found the magic ticket if you ask me. I wouldn’t bat an eye about that being too low level or breaking api change. A new editor could come out tomorrow that would replace Atom for us!
I was worried about some direct DOM prop changes I made in my code, months ago. Haven’t seen an issue since.
I’ll just throw this out there for fun. When I was working on a sublime version of Jumpy I had some weird similar issues with buffer. At some point I was overlaying a file, naming and saving a temp file was a trick, not a good one. I then ended up getting rid of that overlay and doing inline edits, but I fortunately could run the undo command and it would not prompt me for saves if I remember correctly. What I really wanted was a way to do things with overlays etc, of course super easy to do in Atom!
Does your new editor need to be a real editor (sounds like it might)? Or can it just be a z-indexed div with read only stuff in it (preferable)? I think that’s the better approach if your plugin is doing a read only overlay / display of info. I remember your read only editor question from a while back, so I might be blurring the expected behavior here…