The cause of the error has been identified:
For asynchronous operation I capture the data pointer (to avoid memcpy) provided by my SSLWriteFunc callback triggered by SSLHandshake calls so I can queue the bytes to be sent on my library's custom kernel queueing pipeline after returning from SSLHandshake. On Intel and iOS arm products prior to M1 support I observe the bytes at this address are still valid after returning from SSLWriteFunc callback but on M1 these bytes are already zeroed.
Despite that it doesn't help me in the present I thank you for your response. However, as long as there is production code somewhere still relying on SecureTransport and doing truly asynchronous writes/reads with the underlying socket this matters to the world just not to Apple. What I'm hearing is even though we are savvy enough as a company to make no guarantee we wouldn't do this, we broke expected empirical behavior between the way the library used to operate with CPUs in our old products and the fact that you are developer that spent his slim amount of hard earned disposable income on our new architecture specifically to port his libraries and applications means little to us. But that was always expected and I thought I'd give the forum a try anyway.
The reason I'm not ready to tackle updating to Network yet is because I am in the middle of a long winded cross-platform feature addition resulting in significant architectural changes that originated on the other platforms I support. Again, I haven't had the professional cycles across all the fields I am obligated to dig into yet but one of the things I'm skeptical of is that it's going to provide road blocks for async non-blocking + direct BSD socket access that SecureTransport didn't and I know you are Apple and all but I still like to verify the integrity of each and every modern and legacy library you've published independently, and if you left something out of a "modern" replacement that I require I'm going to reach for the deprecated one.
I still intended to expose SecureTransport as an option for client code relying on that path after I integrate with Network. I'm not just going to throw that code away. After I shown that I've integrated with Network then will I be worthy a non-boiler plate response when filling a bug report re SecureTransport?