You will get the usual stuttering in cases a) and c). You just make two full-frames out of two fields with this, that’s all. Every section that used pulldown (80-90% of an episode) will stutter, because no doubled frame had been decimated. It’s harder to realize with cartoon, because of natural frame doublings, but try it with natural content.
There is no way, really no way, to get this stutter-free without removing (decimating) the doubled fields (after correct TFM, the doubled frames) of pulldown.

And, by the way, for the b)-type (original 29,97 cgi) this is not the best way to handle either. TFM is a field-matcher, and if you use it on really interlaced content there is nothing to match, because each field has been taken (created) at its very own time, no progressive frames to reconstruct, because there are none. So if the origin is really interlaced you will get
-TFM upper field --> result = interlaced, because there was nothing to match --> post processing of TFM realizes this and if not set to 0 deinterlaces (but not with the best possible quality)
-TFM lower field --> the same, maybe there is a switch that uses the other field for post-processing-deinterlacing, I am not sure at the moment, if not you will get twice the same.
So you get two parts where no TFM-field-matching happened, but only p-p-deinterlacing in rather medium quality, because TFM is not made for this situation. The p-p-deinterlacing is made for the few frames that couldn’t have been matched correctly in an a)-situation (pulldowned 23,976-material).
If you want each field’s content in full-size in 59,9 you should simply bob with highest quality (QTGMC again).