1:
Not necessary for the very first time Bash is run. Bash will generate a blank patch if it isn't present the very first time Bash is run. It only does this check once though, so if the patch is deleted (or Oblivion reinstalled, but the bash settings are kept) it won't regenerate the file. So it's probably best to keep the current wording just to be safe.
It might make sense to have Bash generate the blank patch any time it goes missing. Though it may annoy someone who uses Bash but not the patch.
2:
Lock Times should be enabled unless you use a different program (OBMM) to order your load order.
Auto Group is ignored unless BALO is enabled.
4:
Footnote, with CBash, Mark Mergeable isn't necessary (except to color code the mods properly). CBash checks the mergeability status of each mod every time the bashed patch dialogue is opened.
6:
You may want to change the selection keys to be more friendly to those that are red-green color blind.
"only select mods in the right hand pane for mods you have installed" should it be "only select csv's in..."? Either way, it's confusing. Perhaps "only select mods in the right hand pane whose item names you want kept"?
The .csv note is misleading. Csv files may reference multiple mods, and any mods that aren't active will be skipped. This allows you to build a single csv file that changes many mods (much like filter mods). For example, you can rename the items in 100 mods, but have it in a single csv. Only the mods that you have will have their items renamed. So it doesn't hurt to check a csv even if you don't have any of the mods (but it doesn't help either, and may make the patch take a little longer).
"If you have no mods..." isn't true for Race Records. It should be ticked even if there's nothing on the right.
One feature of csv files is that they override all mods...they're treated as if they come after every mod in the load order except the patch. Dunno if that should be mentioned since the guide isn't aimed at advanced users.
9:
Only needed if the user renamed a mod.