I like fireyone's idea of just overwriting with a blank template after a cclean. Easy enough to just give the script a shortcut so you can run it from an icon or menu.
What I would like to see in CCleaner is a "script/process to be run before/after CCleaner executes" entry, so that people can run tailored jobs before or after CCleaner has executed. There are so many disparate requirements* that it's impossible to build everything into CCleaner ... and indeed things that people would logically want to incorporate at the end of a CCleaner run on their own machine wouldn't fit logically into the mainstream product anyway.
*For example, actually editing (cleaning) the content of files natively within CCleaner is a huge task ... people could have vastly differing requirements for different types of files and file content ... and anything but a very basic generic syntax (e.g. to use in a custom .ini file) would be a big ask.
Set objFSO = CreateObject(“Scripting.FileSystemObject”)
Set objFile = objFSO.OpenTextFile(FileDirectory, ForReading)
Do Until objFile.AtEndOfStream
strLine = objFile.ReadLine
If InStr(strLine, LineToRemove) = 0 _
And InStr(strLine, NextLineToRemove) = 0 _
And InStr(strLine, CleanUpLineToRemove) = 0 _
And InStr(strLine, FinalLineToRemove) = 0 Then
strNewContents = strNewContents & strLine & vbCrLf
End If
Loop
objFile.Close
Set objFile = objFSO.OpenTextFile(FileDirectory, ForWriting)
objFile.Write strNewContents
It would probably be much simpler for the folks that make Notepad++ to implement their own cleaner. Then again the batch script trick of replacing the file with an already cleaned version would suffice, and is something I do with programs that operate via an INI file.