No matter which health check path I provide, even if it's completely arbitrary text, the health check will only pass as long if the matcher code is set to 0.
I have one service that's just using the default path given by the AWS example - /AWS.ALB/healthcheck. It's passing with a 0.
Another service has implemented a specific health check path that returns 1 on success, but the check continues to fail unless the matcher code is set to 0. It's worth noting that this service has implemented server reflection.
Am I missing a piece here? I more or less followed the setup in the official example.

Per the official GRPC documentation on response codes, a response code of 0 indicates
This would be the correct return value for a health check that has passed.
I'm not sure where the blog post you linked to got the idea that a response code of "12" (UNIMPLEMENTED) is indicative of a health check passing, but this certainly shouldn't be the case.
You should definitely be aiming to have your GRPC services return a code of 0 for success as this is the standard mechanism for indicating a healthy service.
I have embedded an image taken from the linked website in the event it is not available for future viewers.