Okay, we've done a slight workaround. Now, due to the size of the db itself, crawling chapter data is really not a good thing for us. However, when the form is triggered has been moved to the first time a user is trying to look at a chapter. This then sets the cookie, just like it did when trying to access anything at all.
We've replaced that with a simple cookie, which has no forms in it, and is set by clicking a link. The downside to this particular cookie, is it must be set per subdomain. It does last for 30 days, so only needs to be done once a month. Not a big deal, really. It still covers the site by clearly stating the age requirements needed to access, which is important.
Hopefully within the next week, we'll see different results from the crawlers, where they can index the members, the story listings, and etc. Just not the chapter content.