I use two plugins Vim shortcuts and Vim Editor. My experience is I regularly use the shortuts plugin , but I rarely go into ‘Vim editor’ mode cuz
1 - you have an extra operation to press cmd E - vim is all about efficiency, adding an extra operation is against the basic philosophy 
2 - Handling multiple blocks is kinda hard.
3. The page control doesn’t come back automatically when you :wq the block being edited. You need to click somewhere on the page to get the control back.
4. Can’t create new blocks (I think).
5. Doesn’t catch my vimrc… Without that the features are not exciting enough to go through all the pain.
Thus I am missing vim while writing a long block …
A native vim experience for entire page is absolutely must for native vim users - something like Atom or vsCode.
On the other hand , building a vim experience (the one that a vim user craves) is like boiling the ocean. Because no matter how much you build in logseq, a serious vim user will always default back to command line mode. A much used tool thus be, building a logseq plugin for vim. This will bring the graph benefits of logseq to vim and at the same time introduce logseq to a much bigger vim user base . Basically we need either a logseq-CLI that natively opens vim for every page and tracks the blocks in there, and/or a vim plugin that allows me create blocks and pages and link them in a graph.
In absence of above two - native vim experience in Logseq, or the logseq-CLI, I simply need to split my work - notes and random thoughts in logseq, serious writing in vim.