So, I'm a little unsure of your question here; certainly have to agree that the 'eCSR*' stuff appears to be missing from the ER Diagrams (TBH, I haven't looked at them that closely before). I'll open a ticket on that with the product team but as you'll see from the documentation of similar views (e.g. eAgentLoginStat) it's pretty scantly covered.
As to the keys and indexes, those views don't have primary keys defined (and, in fact, there are none in the ER Diagrams just linking fields (FK)) and I'm unsure why indexes are relevant (outside of performance which is an implementation detail). It seems logical (implied?) that the contactOriginatedStamp + CCMID will be unique but, since these are not relational tables, I would not imply an actual constraint on the data. As I say, I think I'm missing the question.
Apologies I'm not understanding better but, please, feel free to open a [technical ticket] if you want further support and, perhaps other community members will better see the specifics of your question and assist.
--
[technical ticket]:
https://www.devconnectprogram.com/ticket/technicalTicket