Why disabling a clustered index makes the table inaccessible?

Question

When an index is disabled, the definition remains in the system catalog but is no longer used. SQL Server does not maintain the index (as data in the table changes), and the index cannot be used to satisfy queries. If a Clustered Index is disabled, the entire table becomes inaccessible.

Why isn't it possible to access the data directly from the table discarding the B-tree? (most likely by scanning the table row by row) Wouldn't that be more appropriate than making the data completely inaccessible?

It's a purely theoretical question - I would never actually do that. It's not a scenario, nor a to-do thing, I just want to know why thing goes that way, consider it an internals question.