VS Code’s extension system makes it pretty easy to build your own code snippet extension. I use my own private extension to easily “generate” different types of markdown files (ie readme vs a troubleshooting guide) from my personalized snippets.
I agree that data staleness is a limiting factor. Depending on your needs and technical proficiency you could use use their zimit service (limited in the number of links it follows). The zimit tool is oss and on github, so you can run the it yourself to keep the sites you are interested in up to date in your local kiwix
While not a solution right now, I just want to add that the general transit feed spec aims to solve the data interoperability of different transit systems. The transit system keeps a publicly accessible zip file up to date, and then anyone can pull/parse the schedule/prediction data in a consistent way across transit systems. I know in the us adoption is slow, with vendors prefering to build their own walled gardens and transit agencies lacking the vocabulary or skills to advocate for more open data/tools
i like Taskjuggler, but it may not check all your boxes. specifically there is no kanban or issue tracker built in. It has very basic note capability, so i combine it with markdown files to keep a list of issues, risks, dependencies and references associated with the large projects we are working on. I use a kanban vscode plugin which uses Markdown front matter to set the status and next action date. Taskjuggler has a learning curve, as it is text based and the files that define your projects are stored in source control and need to be transpiled into html reports. It can track time granularly with the bookings feature, although tbh i have never had a need to use that, the basic scheduling has given me a good enough for my need view of resource allocation.