Oh, I was suggesting to set the PATH only for the terminals you use. I think someone else who can actually tell how things are organized on a KTouch could go into details and e.g. explain how to set session settings.
And it's in fact a bit different situation as for consequences for the boot sequence: Non-existing paths are ignored. Bash won't kick in, however, since other scripts will probably use absolute path (#!/bin/bash) instead of that "env" trick (which will search the PATH for the named executable).