One of the absolutely most offensive things I see wrt Perl is the practice of calling a Perl script from a Perl script.

Why? Other than just bad taste, you are unnecessarily burdening the operating system with the overhead of creating an additional perl interpreter, invoking all book keeping required for spawning and tracking child processes and memory. Oh, but it's just one extra process, you say! Well you keep doing that kind of thing and your CGI script grows in popularity and size - suddenly your server load is about 8,000 times what it should be. Do not laugh, I have seen it happen and continue to happen.

Turn loadCSV.pl into a modulino - it can be done in very few lines, even if it's a monolitic Perl script from 1974.

End result in your caller (not the best practice but will save you an OS process fork:

  use FindBin ($Bin);
  require qq{$Bin/relative/../path/to/loadCSV.pl};
  my $out = your::modulino->run( (qw/-L -Q/) );
  print $out;
[download]

There are a million places to find informatin on modulinos, it's pretty much as simple as:

package your::modulino;
use strict;
use warnings;

# Note: I know this is awful but it's better than what OP is doing now
print __PACKAGE__->run(\@ARVG) if not caller;

sub run {
  my $self = shift;
  local @ARGV = @_;
  # shove nearly all loadCVS.pl in here, getopt and all with ONE excep
+tion
  # ...
  # convert all of your "print" statements such they create the string
+ you
  # were going to print, then:
  return $formerly_printed_stuff;
}

1;
[download]

The above is dirty, but better what you're doing. And it provides the basis for really creating a well done modulino. Or better yet, an actual Perl module where the CLI version becomes a 3 line script calling the dern module you just peared off.