@treebtc I build ink! analyzer and I would second what @hitchhooker advised above.
You’re better off extending existing IDEs/editors via plugins/extensions than building something from scratch (or forking and maintaining one) IMO.
ink! analyzer is (at the moment) focused on intelligent editing features for ink!, while you seem to be more interested in debugging features generally.
I’m working on an ink! analyzer equivalent for FRAME, some discussion here, but that will be focused on intelligent editing features as well (at least initially).
Under the hood, ink! analyzer implements Language Server Protocol (LSP) which allows the same low-level infrastructure (i.e. the semantic analyzer and language server) to be used with multiple IDEs (not just VS Code).
For debuggers, there’s a similar Debug Adapter Protocol (DAP), so I’d advise checking that out if there’s some domain specific feature that you can’t get from existing debuggers and debugger extensions (e.g. VS Code has an LLDB extension and IntelliJ IDEs support both LLDB and GDB).