I'm not aware of a scheme that does this, but I'm not an expert so there may well be such a scheme and I just don't know it.
As I see it, the main issue is that most code-based crypto uses linear codes, and truncation is a linear operation. So correcting a truncated codeword (also known as erasure correction) can be done efficiently even if you have a randomized description of the code.
You could mix errors and erasures, but (depending on the scheme) this might just be equivalent to encoding with a shorter code and then adding errors -- which is to say, it might be the same as an error-only scheme with different parameters.
Also, for some code-based cryptosystems this trick seems inapplicable to begin with. For example, although the original McEliece cryptosystem sent corrupted ciphertexts, modern versions of it such as "Classic McEliece" are based on Niederreiter's improvement, where you send the syndrome instead. I don't see how truncation would help there.
You might be able to do something in the direction you suggested though, where instead of truncating you would round to the nearest codeword of a second code. Or maybe it would work with some kind of code where the truncation operation works over a different field than the encoding operation (or similar) so that it's not just a linear operation. Or maybe you could use a deletion-correcting code, and delete data from random locations within the codeword.