[plagiat0r]

Every bit of information that is stored in the DNS is serving one basic purpose: to allow connection to a string. Additions, like CAA or SPF are also consumed by programs to set some limits of a domain usage.

Every other record you mentioned never gained any adoption, simply because this "database" is meant to be used by programs, not humans. Sure, I may use SOA email to contact a DC, but this is exception, not a rule.

Therefore, from the perspective of a person that does DNS courses for technical staff, I conclude that average Joe will never be able to set TXT records properly, and professionals will not do it either because of the reasons I mentioned.

And while I encourage you to pursue your goal, adoption willy be close to none so I'm not so worried about that. Adoption of this will be much lover that adoption of HWINFO or LOC records (ignore RFC 8482, I mean user provided HWINFO data). Your proposal will be used by 50 people total, optimistically.

For all use cases, we have http invented already. Storage for http is also a solved problem.