Aside from making pin access easier for TritonRoute, there are other reasons I wanted the RAM to be completely obstructed and unknown to both the router and magic (for drc), which emits millions of errors otherwise as the LEF view isn't enough of an accurate representation. This is not really an issue with OpenRAM per se; the same probably needs to be done for any macro generated independently from the flow.