While it’s great to hear that you guys are working on this, the news that you are pursuing a hardware specific cause is a bit disheartening, for me at least, as I am experiencing a very similar issue on a quite different machine with different internals (2013 Mac Pro, details are below)
Shall I chase for a resolution on that ticket separately or will it benefit from your specific testing efforts for @mavmcl 's issue?