This is really only necessary though if you wish to compare your own personal TSS values to those of others who use FTP as their performance anchor point. If your main priority is to examine your own training patterns then using CP as your fitness anchor point will introduce a uniform systematic downward bias to the TSS values. These are arbitrary units anyway so the absolute value itself does not matter. It is the loading pattern over time that is important, and this won't change.
A workaround though is to enter both FTP and CP into the athlete properties and give them both some date way off in the future. Then just make FTP current when you want to examine TSS (and compare those values to others) and make CP current when you want to examine the W'bal model results.