LCP measurement reported without the LCP DOM element

### FAQ

- [X] Yes, my issue is not about [variability](https://github.com/GoogleChrome/lighthouse/blob/main/docs/variability.md) or [throttling](https://github.com/GoogleChrome/lighthouse/blob/main/docs/throttling.md).
- [X] Yes, my issue is not about a specific accessibility audit (file with [axe-core](https://github.com/dequelabs/axe-core) instead).

### URL

https://www.crunchbase.com/

### What happened?

### Steps to reproduce
1. Run a Performance Lighthouse test on `https://www.crunchbase.com/` in Chrome Developer Tools.
2. Observe that LCP measurement is reported without the LCP DOM element being specified.

### Screenshots

### What did you expect?

When Largest Contentful Paint measurement is available, **the LCP element should always be listed** (since the measurement is derived based on finding a specific element).

TL:DR; there should never be a case where there's a measurement and no element specified (or the other way around).

### What have you tried?

I've ran numerous tests to confirm it's not a one-off behavior. It happens either persistently (every DevTools test) or intermittently, but in a semi-persistent manner. I was also able to reproduce it in Calibre, see this [publicly available test](https://calibreapp.com/tests/f21dfdd/3913749/performance) [^1]:

I wasn’t able to reproduce it on PSI (web.dev/measure), perhaps because it runs on newer Lighthouse version (10.0.2), but I'm unable to speculate the reasoning.

---

[^1]: You can either look for the `Largest Contentful Paint element` audit, or filter by LCP-related audits.

### How were you running Lighthouse?

Chrome DevTools

### Lighthouse Version

Lighthouse 9.6.8

### Chrome Version

Version 111.0.5563.64 (Official Build) (arm64)

### Node Version

_No response_

### OS

Mac

### Relevant log output

_No response_