Clarification on Transcoder & Serializer

So, this is some kind of "meta ticket" because I am not able to figure it out 100%..

• The RFC defines both the concept of transcoder and serializer, but to me it looks like the ruby SDK only defines the transcoder and uses it both in KV and JSON spots. Does it make sense to split this up as defined in the RFC?
• Analytics and Search options expose a transcoder, but query options do not (should be a serializer I think, but in any case should be consistent with the other methods?)
• APIs like analytics, search etc expose the transcoder as getter / public APIs on the result object. The RFC says pretty much "only expose it on the options, and then it will be used in the results" .. so is there a need in ruby to deviate from this? Would it make sense to only allow passing in the transcoder/serializer from the options and dont give access to it (both setter and getter) in the results?