Hi there!
Thank you to @dcartlidge & @hansontools for sharing your ideas 
We've been mainly suggesting sticking with the legacy list view for the time being if you need functionality beyond what @dcartlidge's first example provides
For some context on the launch, we launched the new list view before reaching feature parity with the legacy list view. We wanted to provide the option to benefit from the performance improvements as soon as possible, and we wanted to start getting user feedback as we're working on additional functionality.
As noted on this thread, the new list view still has a notable difference from the legacy one, in that it does't support indexing into child components to access their properties yet (see the scope warning on the launch announcement). This feature is being actively worked on and we are collecting feedback/ideas here. Since the new list view was completely redesigned to have better performance, indexing into child components will also need to be re-written and we want to be thoughtful about how we enable this feature. I'm not able to provide a specific eta for when it will ship, but I will post here if I get any updates internally.
We will not remove the legacy list view until we are confident that there is complete feature parity between the two, and therefore no reason to keep them both. Even when we deprecate a component (i.e. move it from the list of legacy components to the list of deprecated components), you can continue to use existing components in your apps. We only remove the option to create new deprecated components, and we usually maintain an option to still add new deprecated components behind feature flag - just in case!