I wonder if it's useful that read-textual-bytestring reads from '#u8"' prefix.  It means the caller most likely already knows that input begins with the prefix.  In general parsing cases, though, the caller knows the input is likely to be srfi-207 bytestring _after_ reading the prefix.  Practically, would it be more useful to have a procedure that only parses the content part?