What exactly do you picture your 3D print service generating?
The fundamental problem is that determining ECC support is like trying to ascertain the octane of the gasoline in your gas tank without getting out of the driver's seat. There's actually no reliable way to do it across the PC landscape, so the referenced Jira ticket is just basically asking for something that can't be done reliably.
As nice as it would be to
Please make life better and stop pushing certain "known good configs". it is not helping anyone
from the Jira ticket, even the dedicated memtest86 products, whose whole raison d'etre is to test and report memory, do not reliably and correctly report this for every platform, and these people have made a BUSINESS out of trying to keep track of which chipsets do which things, and how the data is reported. They STILL can't get it right.
The reason we push "known good configs" here on the forum is because that's actually the only viable solution to the problem.
One reason iXsystems sells prebuilt systems is so that they can know that the components used do in fact support ECC.
So, having provided some context, and now looping back around to your reply,
one thing I can think of is that one does not need soldering skills when using my suggestion, only a 3d print service locally.
Also one does not need to sacrifice a test DIMM. Rather have the actual DIMM tested.
Does this make sense or still not hitting any marks? If no one sees it then at least I gave it a try
What do you envision your 3D print service doing?
If we are testing for ECC functionality, then presumably we don't already know that the chipset supports ECC correctly, or reports it usefully. This means that you need to deliberately and reliably be able to inject an error into the data. That involves corruption of the signals at an electrical level. I have no idea what you believe 3D printing could do to help you here.
Those of us who are "in the biz" will often have a few DIMM modules around that are known to be flaky. This, or deliberately injecting errors into a good DIMM, would seem to be the only options for end-to-end testing for ECC.
Otherwise, you would need to try to collect platform-dependent information and try to infer what you can from data that may exist, may not exist, and will definitely vary in quality from platform to platform. There is no way to do this correctly without hardware support, and the only way to validate would be to deliberately inject errors.