... All of them should be in /etc/init.d/tc-config.
Hmmm, that might be the case for the majority of TC specific boot codes. But in the Core there are some other scripts that interpret these TC specific boot codes:
(ignoring for a moment: '/etc/init.d/tc-functions', and '/usr/bin/showbootcodes', plus some executables like '/bin/busybox', '/sbin/udevadm' and '/sbin/udevd' which probably interpret some more generic boot codes)
If adding the default TinyCore extensions (e.g. from the 'cde' directory) there are some more:
(and ignoring again '/usr/local/bin/stats')
Please note that these lists are only containing files that directly interpret '/proc/cmdline'. In many cases the result of such an interpretation is stored in a file (e.g. '/etc/sysdir/icons') and several other scripts then use said file. So there are many other "secondary consumers" of TC specific boot codes.
Therefore I'd like to state that whilst I also use '/etc/init.d/tc-config' as my first stop when trying to figure out the treatment of a given boot code, one has to be aware that this is likely to be a necessary, but maybe not a sufficient approach.