Historically there have been issues around daily pullers (likely multiple), but I haven't gone looking to see if B* still works or not honestly.
It was such a stupid implementation anyway with so many easy fixes that I'd be absolutely floored if EQ / TU haven't fixed it in the last couple of years: it's a utterly serious flaw in their software as it means their data can't unilaterally be trusted as a result of the exploit, and for companies who's business is by definition about the accurate reporting of data, well... get off your tookuses.
Anyway, I would continue using the services as designed as you are and not worry about it. For all our harping about it, a split file, if it does happen, can be resolved albeit you'll have some amount of work you'll have to do to fix it; also if IIRC the people who were purposely doing it were using multiple daily pullers.
If you're really curious you can take a look at the TU data pretty easily for SP's and see how many your service is logging; I just checked mine as a result of a dispute and while there was some wierdness in how CK was reporting (4 just today for SP's!?!? And a couple from the last six months) and there's been a lot more data refreshes than that, so I suspect there's some preventive measures in place.
