I am still looking for a repair solution using VBA scripting from within Outlook, but getting dizzy from trying to find/bind to my corrupted folder through the Outlook object model. As a simpler alternative which circumvents the complexities of Outlook's Object Model, I was able to export the corrupted contacts folder to a csv format file and make the necessary programmatic repairs using VBA scripting in Excel, a much more familiar environment for me.

Because Excel csv files cannot contain macros, the csv export file from Outlook was loaded into Excel and saved as an .xls workbook with macros explicitly enabled under Options>Advanced>Security Trust. After I make another backup export of the corrupt folder, I will save the Excel .xls worksheet in csv format and import it to Outlook. If anyone sees anything wrong with this plan, please give me a heads-up.

Also, if anyone sees what I am doing wrong in finding/binding to the Outlook folder in Outlook VBA, please let me know.