From my experience, the CLR itself is always going to be disadvantaged when trying to write to the DB (the CLr best practices advocate avoiding writebacks for this reason). The best advice I can give you is - don't do the write-back within CLR. Have the CLR generate the results, and insert them using "regular" T-SQL.
Insert mytargettable(mycolumns)
Exec MyCLRGenerateAndSelectProc
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?