Isn't the binary data processed anyway (e.g. quoted to be inserted into a SQL statement)? Perhaps bindings in some SQL drivers can avoid that step?
Anyway, if the SQL glue knows about the data types involved in the query (and in the table definition) then I suppose that info may be used to apply UTF-8 conversion selectively.