Performance issue with a lot of tracks.

The app has always had issues with performance related to tracks. Im accumulating quite a number of tracks now (in the hundreds for some areas) as i track many of my hikes with my dog. I have a goal of walking all trails and footpaths in my city..

Ive been thinking about this, and I think it is solveable if there was logic in the app that would prevent/limit the individual rendering of tracks when they are very close to one another.

Ie. if you have a footpath with 25 tracks the rendering logic for tracks would detect this and merge the resulting track as an average of these 25 tracks. Of course this would only apply to tracks that are very close. Preferably the user would be able to tweak settings related to this, ie the distance between tracks that would be rendered as one. For visual clarity we could also make these combined tracks render with a thicker line to make it clear that its a combination of tracks, and if you zoom in enough it could split them apart and render individually again. And it would probably need testing for areas like the attached, but i think it would tremendously increase performance.

Im not sure if this is a widespread issue tho and I realize that it probably won't be highly prioritized if at all, but for me its really affecting the use of the app in certain areas where i hike a lot.