Can "rbind" be used in Kickstart?

Issue

At present our standard install involves creating a large LV (called: lv_shared) and during the post install we create "rbind" mount points for the following directories:

/home, /tmp, /var/cache, /var/lib, /var/log, /var/tmp, /var/crash, /var/spool

This is to prevent users/applications from filling up the root filesystem.

So a typical filesystem layout for a new system would look similar to:

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg00-lv_root
                       18G  4.5G   13G  27% /
/dev/mapper/vg00-lv_shared
                       49G  5.0G   42G  11% /SHARED
/dev/cciss/c0d0p1     487M   46M  416M  10% /boot
tmpfs                  36G     0   36G   0% /dev/shm
/SHARED/home           49G  5.0G   42G  11% /home
/SHARED/tmp            49G  5.0G   42G  11% /tmp
/SHARED/var/cache      49G  5.0G   42G  11% /var/cache
/SHARED/var/lib        49G  5.0G   42G  11% /var/lib
/SHARED/var/log        49G  5.0G   42G  11% /var/log
/SHARED/var/tmp        49G  5.0G   42G  11% /var/tmp
/SHARED/var/crash      49G  5.0G   42G  11% /var/crash
/SHARED/var/spool      49G  5.0G   42G  11% /var/spool
/SHARED/opt/some_app   49G  5.0G   42G  11% /opt/some_app

Setting up the "rbind" in the post install is inefficent and time consumming because the files need to be copied to the /SHARED/xxxx directory and then removed from the original location before the rbind can be mounted.

Is there a way we can configure the "rbind" before or during the installation phase?