I literally just dont think so. The diagrams shouldnt be IN the freaking device it should be in the box on the manual. Also from my ubderstanding framework doesnt provide a bunch of low level documentation which i also think should be included. Old devices, old tvs, etc could have complicated assemblies and you had to be tech savvy to take it apart, the difference was they made it possible to take it apart. In the same space framework provides 4 io ports you could put all the io that could be possible and still make it repairable. You can use daughter boards instead of whole physical assemblies and save a bunch of space and reduce on mechanical assemblies you need to keep all the parts together. For example on a desktop device where you had more space old devices would use a fuse panel but on a handheld radio you would need to take out a few screws and only then could you replace the fuse. And the manual and wiring diagram was on a piece of paper you got in the box. It was to save space. I think its a completely worthile investment. The problem most people face when designing something like this is its hard and they either cheap out and make it hard to repair or waste resources on complicated mechanisms that could be achieved in an easier way. While this isnt such a big problem on a laptop, when you get to phones it is a hard balance. Of course if you legally force companies to comply with RTR then suddenly they come up with really good ideas to balance cost, complexity and repairability which is what we should do.
Sorry for the rant btw this is just a space im very invested in and have a lot of opinions about so i wanted to share what i think.
Maybe you should fix the systematic problem instead of doing surface level fixes that impact the freedom and mobility of minors.