AFAIK, the only difference between codium and vscode is that telemetry is stripped out. I haven't used it, but I imagine it's great. It works the same as vscode in other respects. (unless someone corrects me here).
The main issues I have with the vscode/codium approach is that remote ssh works by installing and executing a server at the remote location (including installation of extensions).
To me, this is convenient but risky - it necessitates prerequisites on the remote server (which caused issues for older server installs), it leaves stuff behind on the remote (if you just want to edit a config why would you want to litter the remote server?). Fundamentally I'm not sure why this isn't a very, very serious potential vector for malware - others can correct me. Do you want to inadvertently put 3rd party nice-to-have extensions written by just anyone running remotely?
They could mitigate this by having an official extension than has an option to do simple sftp access with local caching (as is done with many other editors like UEdit, npp, mc, vim, etc...). Most 3rd party extensions for this that I've seen seem very janky. It begs for something official.
My other issues with vscode are subjective - it lacks virtual space editing, and, frankly the whole thing is a bit slow for me. Again, this is subjective.