That attitude is part of the problem - thinking of it as a terrible burden. If your secondary environment is set up properly, moving from primary to secondary should be a non-event. A little change and the business is working, monitoring is up and running, no one really has an issue.
The problem is that a lot of LOBs treat BCP as a separate environment from prod. So they go days/weeks/months with prod and bcp out of synch. They don’t do validation when they do releases and as a consequence when they do have a forced test or heaven forbid an actual event, it becomes an incredible PITA and hours long incident trying to get the environment to work properly.
We deploy our apps to both prod/bcp on the same night. We validate each on the same night. We have two BCP failover test per app each year. Then there are the Enterprise events as well. These are all non-events. It’s a couple hours over the weekend to failover, test, fall-back and everyone is done. We see other LOB’s doing the same exercises and it takes them all weekend to become successful after hours and hours of work, or they fail and suffer from the management questions about why they failed. Better planning and maintenance of your BCP environment makes life much easier on all those involved.