The map works well and was done in a reasonable amount of time, because it's has complete access to the whole GSX data and memory, since both GSX and the map are just part of the same Python code running under the same engine, so they share all they know about each other very easily.
An ingame panel (and if we'll ever undertake that, it might be an EFB app, so 2024-only) runs in a completely separate environment (the HTML/JS framework) that is not so well suited to exchange data with an external app, you can see some example in the GSX menu: it is a very simple code, but it's hampered by limitations imposed by html/js framework that hasn't been designed to easily share between external apps.
We still have annoying issues (the main one is your code doesn't run anymore when you close the panel) and GSX only needs to exchange a few lines of text of the menu choices and the user commands, the 2D map would have to share a lot more data with GSX, so there would be a lot of overhead and we still would have the same limitations we already have with the simple menu.
That doesn't mean it will always stay like this: sooner or later, we would like to redo the whole interface from scratch, especially since the SDK IS improving on this side, but it would mean it would be 2024-specific, of course, since we don't expect the 2020 SDK to ever be improved.
