I've been trying to optimize blocks of code originally written in shell script.
I converted these blocks into perl, awk, and sed files and later compared them in file size, preformance and execution time.
Now I source the individual files as needed throughout the shellscript.
But I'm wondering, if I create a script that sources a perl script, an awk script, a sed script, then would that increase the cpu/gpu/ram usage and slow down the execution time?

Measure the MIPS.

As part of your efforts with optimizing these scripts you must have learned where high load tendencies are, be they dispatch logic, computations, loops, file operations, or other things. And further, there's little point attempting to optimize execution time if you haven't determined what was formerly consumed, as well as what is consumed now.

@shirase, I heartily applaud what you are doing, and I have done it many times myself. "CPU/GPU/RAM usage" – these days – is entirely irrelevant (IMHO) in contrast with the purely human(!) considerations of clarity.

The only "shell" that I am aware of which attempted to include a "serious" programming language was Dr. Korn's ksh, which today is rarely used or even spoken of. The very-primitive scripting capabilities of bash certainly do not qualify. But, this is precisely why we have the "#!" ("shebang") feature, which allows any(!) language to be used to implement "a shell script."

These days, we have "hardware resources in embarrassing abundance." But we still spend a fortune (the recipients call them, "salaries" ...) on the humans, so we do not want to waste these humans' time ... time spent "puzzling out" what the code in front of their faces actually does. (And especially, "getting it wrong.")

Now – to be fair – much of the code that we still encounter today was written at a time when "hardware resources and memory" were at an absolute premium. The programmers of that time (koff, koff ... ) did what they had to do, using the only thing they had: toys.

As you proceed with your efforts, be sure that your team recognizes this as a formal project, and applies necessary "deployment" and "quality assurance" efforts to it.