Footnote 1 says "Historically, the CHERI compiler would select the left-hand-most pointer in the expression as the provenance source.". This is still true, we just warn about it.
Footnote 2 says "We could add a data-flow-sensitive analysis to determine whether values are the result of promotion from a non-provenance-carrying type." We should note that such analysis would almost certainly occur after optimization passes and thus would have optimization dependent results. It would not be dependable either for generating compile time warning or at runtime for program correctness purposes. Such analysis could be used to inform the correct annotations in code.