Yes to getting rid of follow/mute lists. I'm already in the process of this with using other lists and may end up pushing those into relationship status if enough clients add support

No to getting rid of bookmarks lists/sets, authors lists, curation sets.  Some collections are relatively static and do not need to be defined dynamically across a series of notes the way that relationships work.  Plus, lists are the best way to give contextual order to related data, and allows for duplicate entries within the list.  Curation sets are actually Curation lists.  

 We think we can blow the usefulness of static lists out of the water with embeddings, but not everyone wants discovery that powerful because they find it uncanny.

At any rate, the list structure will remain (our own 30040 index uses it, to create an ordered list of chapters for a book) and people will continue to use it, but I'm eager to put everything on the table and give it a good look.

Where do lists make sense and where not? I think we need to just ask that question, straight-out.