Another way of sorting data is to look for rare variations on Enlis (that are not clinically significant/pathogenic - so it wasn't yet pulled out by the above method) that are also on the MitoD database. This is extremely time consuming, and often provides false leads due to either 23andme having an error in calling the snp, or it being reversed for the rare allele, or Enlis calling it rare when it's not. I have no idea which it is or some combination of all of the above.
Here is an example. I filtered my 23andme results to look for rare mutations (2% or less of the population has it) on Enlis where I was homozygous for having it. So a very rare combination. Then I ran those very rare mutations where I was homozygous to see if they occurred on any of the genes that were in the MitoD database.
I came up with 11 of them. That is running my 23andme data through Enlis came up with 11 homozygous (x2) rare mutations that were also on the MitoD database. You would think if it was this rare, my mom would be heterozygous (x1) for these, and my father would be heterozygous for these, and my husband wouldn't have any of these. Nope, for the most part everyone in our family was x2 (homozygous) or almost everyone was x2 for these supposedly rare mutations. Therefore, these get thrown out.
The 11 snps I found useless where it said I was homozygous rare were:
rs189362, rs2126115, rs5927969, rs5928196,
rs2806233, rs13066381, rs17064653, rs11749784, rs439954, rs244411, rs8082645
Therefore, using 23andme data this way didn't help in my search.