The standard reply to suggestions of this ilk is “that sounds like a good idea - why don’t you do that?”.
Most “extra bits around osm.org” (and quite a few bits at osm.org itself) started off as external projects and “became part of the project” because they were proved to work and people found them useful.
If you have a go yourself**, you’ll see what API calls are available, and when you deploy it you’ll encounter some of the challenges and have to figure out how best to deal with them (for example, if a way has changed but no nodes - do people want to know about that? What about relatons?). On the way to creating something I’m sure you’ll have lots of questions, and you’ll be able to ask those here.
** the Garmin map creation process that I used to use a few years ago did originally have some element of this, but I never found a way of doing the extra API calls efficiently with the tools that I had available at the time. There are definitely avenues to explore if someone’s keen, though.