I should really refresh my memory of the tabix code, that'd answer this straight away. I know that there's code to deal with starts/ends, since a tabix index is basically an R-tree for block gzipped files. The question simply becomes whether the parser handles VCF files in an intelligent way or if it just blindly assigns start and and coordinates based on the same VCF column.
Edit: Note that if what I wrote above makes no sense to you that that's not something to worry about :)
Is it a SNP that you're getting at 7073962 or a longer InDel? The latter would overlap your specified range.
I don't think tabix looks at the bases when indexing. It only uses CHROM & POS.
True, you're probably correct then that this is a 0 vs. 1-based issue.
It's not clear to me if tabix always uses a 0-based coordinate system.