If your only reward for beta-testing is "early access to latest features" (i.e. no rewards afterwards) most people will assume the only point is indeed "early access to latest features".
Many companies do this to test the robustness of their system by letting people in in controlled beta-invites waves instead of going 0 to 60 in a stampede inauguration. The tight loop you're referring to seems to me more typical of QA/QC testing, which is a paying job. Trying to pass this job into customers is tricky, since most of them are not interested in following tight reporting schedules or writing lengthy standardized reports.