lawman low competent are the majority and should be catered for
That is likely true. However, it's unclear which threat model you have specifically.
Strategy 1 seems like the better option. It is easier to delete profile 2/secondary profile in case you have around a minute of time, which would only show up in forensics. For low competence adversaries, this is likely the way to go.
Is it inefficient? Yup, but that's the compromise you have to make for increased security.
lawman There doesn't seem to have been a thought out strategy by GOS developers to result user profile privacy on a privacy focused phone, which seems strange.
That's because GrapheneOS focuses on security first and foremost. Tricking law enforcement with fake profiles is not really part of their mission. In fact, that's a rather niche use case altogether, if you look at the general needs of GOS users here on the forum.
lawman or if this something the developers need to reconsider with purpose.
I don't think the developers need to address this issue. It makes far more sense to use duress pin/password for these types of problem; that might as well trick low competence adversaries. The project already said that there's no easy way currently to hide user profiles and that forensics could reveal the existence of any profile - which would make all these hacks half-measures - also commonly known as security theater. (I would need to find the source and can't right now, but it's been stated multiple times)