This is exactly the point of not using the false start check. Neither system is in any way realistic. Using false start checks will only add to the mayhem that can be experienced at the start. Network latency will produce the stalls we all recognize as a "real" part of grid starts and simulate someone having mechanical issues. Those folks citing spreading the field out earlier are straying from one of the core ideas of the league. Close and clean racing. Close will not be helped by using false start checks and clean either.
False start checks are all fun and good, right up until you make that fantastic start, but the guy in front of you doesn't, and you get your eye poked out. If you join a series like the RCS, you accept the settings the race organizer has chosen to use and deal with it or not. As Grimm mentioned, I caused start grid mayhem on more than one occasion in that series and inevitably cost myself and others more than one position before we ever got across the start line. It's really not a good feeling to forget the setting is being used and realize at the last minute your method of launch is going to cause issues and there is practically nothing you can do about it. You can warn folks all you like, someone will not hear or heed the warning and it's all for naught.
I tried using the ebrake button so I could still use clutch launches and it was, for lack of practice I suspect, worse than getting a penalty. After failing miserably with that method, I reverted to just ignoring the clutch and left foot holding the brake until the lights went out. False start checks add another layer of complexity that, combined with the variable skill levels in our league, is not conducive to close and clean racing.