LOAD utility should allow huge loads to run with out blocking transactional log files

Please let me explain more about how i look at LOAD utility.
LOAD utility is a way to write data into database quickly by ignoring the traditional route into the system, like query processing insert/update/delete.LOAD utility will by pass many performance toll gates en-route into the data pages.
For Example, it will do direct writes - by passing buffer poolsit will not do data logging into transactional log files and also do minimal loggingit will not enforce most constraints, do not invoke triggers and do not do dependent table data modifications rather put it into SIP state.
When Data is written into DB using LOAD, all performance toll gates are by passed.So why do not consider by pass crash recovery with in a
reasonable limit, so you still stay on the edge of the road but not completely off road. some thing like a privileged lane to cross toll gates with out paying fee or wait time.
The Blocking of transactional log file happens because dbm thinks a log file with load log record is required for crash recovery.But what i am asking is, why to count that log file into available transactional log space calculation.The leeway that i am asking is keep the file in active log space but do not count it into transactional log space used [log files with load log records and all committed transactions will stay in active log for recovery purpose but will not count towards log primary or log second.]So that way i can allow more transactions to happen as long as i have sufficient disk space for new log files.
If the presence of load log record is to provide a starting point for crash recovery that is a different issue.But even a crash recovery process is not done at a table or table space level. it is done on the entire database.
can crash recovery process be modified to refer this load related information from data base directory where load temporary files are stored instead of referring the log record? or it can get the information about loaded tables from table state information or the table control structures directly in the beginning of table space.I do not know the technical changes involved, or the full detailed impact on this but i am only suggesting from a usability point of view.Or Am i missing some thing still in the behaviour of load utility?One final question: If I use copy yes in my load command, it still blocks transactional log files. Please confirm on this point. That is why I am asking for such a change in behaviour.