LSP (Language Server Protocol) modules generally do not provide code-aware syntax highlighting and navigation functionality.
This is where syntax parsing technology like tree-sitter comes into the picture.
Official support for a tree-sitter parser would make creating ‘wolfram modes’ in editors like emacs, vscode, and neovim much easier.
It’s unofficial but LumaKernel on GitHub has released a complete tree-sitter grammar for Wolfram Language. I just tested by wrapping it in a Zed extension and it works amicably.
Look at what you’ve done. Now I need to spend a month using Zed, since I just found out about it from you. 
I have one ‘constant’ editor (emacs) and a huge path covered with the wasted corpses of editors I’ve left behind - BBEdit, Alpha (I even worked on alpha), Sublime, among them; now VSCode. Will Zed be the next in line?
As long as I can slap rough emacs navigation bindings on something I’ll try it. That stuff is embedded in my spine.
Probably I am in a very similar situation to what you’re describing but for me it’s Sublime that I keep coming back to time and again. Having said that, Zed is the one that I have stuck with the most out of everything else I’ve tried.
Care to share your extension/template extension for adding the tree-sitter to it?
WAIT Before you do, perhaps I’ll test its AI capabilities to create one myself? A little meta test, if you will.
How did it go If you are still interested in my minimal extension → GitHub - bbkingisking/wolfram-language · GitHub