This sounds like a new feature (new Bases functions) on top of a feature that doesn’t exist yet (inline properties). You might be interested in the feature request for inline properties that would have to exist first: Native support for Inline (Intext) properties (`key:: value` a la dataview)
As for Bases formulas, you can do .latest() and .earliest() on a list of dates. You can also get a list’s first or last item by index position (respectively, [0] and [-1]). You just need to give the base the list.
To your end, I think Front Matter properties would be a (slightly) more structurally sound solution than inline properties, which are prone to accidental omissions and typos, either of which would misalign your date-status pairings.
Even though Obsidian’s Properties UI renders YAML objects and nested lists in a jarring line of orange text, the YAML is still valid. Bases can read them. Mismatches are unlikely here. And the Nested Properties plugin can help minimize typo opportunities (and render objects in the UI as a bonus): https://github.com/mnaoumov/obsidian-nested-properties
One YAML format for your consideration, natively queryable by Bases:
---
history:
- date: 2026-06-01
status: on track
priority: normal
- date: 2026-09-15
status: attention
priority: high
---
If the whole purpose of the note is to track history, then you could shorten the entries to this type:
---
2026-06-01:
status: on track
priority: normal
2026-09-15:
status: attention
priority: high
---