I noticed that also when using a columnstore index as a clustered index and a non-clustered Hash Primary Key (for in-memory tables). When using dm_db_xtp_hash_index_stats I get one row for a nonclustered range index and 4 rows for the PK nonclustered index (4.7m rows).

I too would like to know why I am getting these kinds of results.