It might fix it, we can try.

Of course, this is part of a bigger problem of routers just being bad with pedestrian routing no matter how we tag things. At the end of the day, we should tag correctly first of all and not based on routing deficiencies.

A similar example where it forces you go along a 4-lane road even though it has `sidewalk=separate`... https://www.openstreetmap.org/directions?engine=fossgis_osrm_foot&route=56.94802%252C24.20034%253B56.94703%252C24.19821

Although I do agree this case could be split into 2 T intersections because it's currently "unnaturally" merged to form.