Thanks for the reply. 
 
Do maintainers recognize this as an issue with having this as default option? There are chances that similar to us other devs/orgs are planning migration in phases to Scarthgap considering Kirkstone getting updates, so this could potentially become issue for others as well. We do have sizable amount of edge systems in production with various CI, and this change broke an important feature and took some time for us to find root cause.
 
I believe correcting is still a proper thing to do and can be planned during any releases.
Additional reference -
https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch05s15.html 
 
Also, it would be good to know what scenarios were considered with this change, probably we are missing some context.
 
 
Regards,
VS.