Anonymization in Timextender REST Connection

Agree.
In our RSD files we are using functions like these:

  <api:script method="GET">
    <api:set attr="method" value="GET"/>
    <api:call op="jsonproviderGet">
		<api:set attr="PersonId_Hash"     value="[PersonId | md5hash()]" />
		<api:set attr="PersonId_Birthday" value="[PersonId | substring(0, 8)]" />
		<api:set attr="PersonId_Gender"   value="[PersonId | substring(10,1) | modulus(2)]" />
		<api:set attr="PersonId_IsTest"   value="[PersonId | contains('TF', 1, 0)]" />
      <api:push/>
    </api:call>
  </api:script>

It would be very useful if we could use things like these directly on the fields in the table builder of the REST connection, to not have to write any personal data at all to our databases.