But the purpose of an SRV isn’t to unproxy anything - it’s to define where a service is. There’s an RFC and everything.
I won’t go into the various discussions I’ve already had on here and with support but wrt unproxying, the issue is that it is trivial for someone to create their own additional unproxied record and specify this in the SRV if that is what they want. However, the current design precludes people being able to ever specifying a host which you do want Cloudflare to proxy.
e.g. There are various situations where the target host might need to be proxied by Cloudflare - e.g. if the service uses HTTPS as a protocol (such as WKD) and Cloudflare act as your SSL termination, or if the service is being load-balanced or proxied via Cloudflare Spectrum etc. The design as it is of substituting a direct hostname in all circumstances actively stops people being able to do this in preference of giving others the convenience of not having to bother creating an additional unproxied hostname to use in the SRV definition if they want an unproxied record.
(There’s other contradictions and bad logic in play too… such as you can specify a Cloudflare-proxied hostname in an SRV record if it is in a different domain! The implementation just hasn’t been thought through properly, that’s all - SRV always seemed a rushed job I’ve reported other previous deviations from spec before).