Looking at how the deserializer works internally I've noticed that the JTokenValue class directly uses json.net. this way the abstraction of the serializer is not complete.
Also setting special options that will affect the deserialization will not be taken into account as the deserializer is created with the default values.
I've not made an indepth analysis at this time, but looking at where the IJsonValue is called (hub calling resolution functions) I think that this will prevent some functions to be called on the hub if you set special rules (let's say for example to handle null or default values, or even custom converters).
running outmof battery power atm :)