You seem to be a bit confused about what "entropic" means. In the context of information security, "entropy" is a measure of the unknown. It is often expressed in bits, which is a logarithmic scale: "10 bits of entropy" means "could assume 210 possible values with uniform probability". Entropy translates to security in that an attacker, trying to guess a value with n bits of entropy through brute force will need, on average, 2n-1 tries. Beyond about 100 bits of entropy, brute force is infeasible because of the sheer cost (not enough energy is produced on Earth to complete that computation).
Being logarithmic, entropy adds up: if you concatenate a piece of data with 20 bits of entropy, next to a piece of data with 13 bits of entropy (and independent of the first piece), then the total entropy is 33 bits.
By definition, a "non-entropic file" is a file with 0 entropy, meaning that the attacker already knows it. Appending a non-entropic file will add exactly 0 to the entropy, so it won't make anything stronger.
When using "key files", TrueCrypt uses a cryptographic hash function which has a nice property of "keeping entropy around" in a much more compact form. A hash function with a 160-bit output will necessarily reduce entropy to at most 160 bits, but the bright side is that it won't reduce it any further. And 160 bits is far more than enough to defeat brute force attacks. Therefore, adding a "non-entropic" key file will not reduce your effective security (but that's because TrueCrypt does things properly).