Thanks for this (and same to others).
It’s clear that there’s an important design issue to resolve here.
I still think there’s technical limitations that mean that the only solution to “real” block referencing also means abandoning the core interoperability principle of Obsidian. This is why I’d bet we won’t see an answer to this until the plugin API is launched and a third-party developer makes such a solution as an add-on.
In the meantime, if you desire block referencing because of familiarity with related app-paradigms (i.e., Roam), your best bet is to forget about the filesystem and to use the quasi-solution I detailed in the thread below. That solution only works if your “blocks” are valid filenames, so it has some obvious limitations.