Compression is already present by default so adding the encryption dataprocessor is sufficient. To confirm inspect the return value of NetworkComms.DefaultSendReceiveOptions.DataProcessors.
Having said that it does look like a bug that adding a second compression step fails. I will create a bug report and we will fix this in the near future.
Regards,
Marc