At least in the example client app, the certificate is hardcoded and used only during registration, so it doesn't seem to add any security when using it to sign the attestation.
It seems like it would make more sense to sign the attestation with the private key corresponding to the public key that is sent at registration, right?
If so we can send a PR making that change :)