Cliff, you know the answer and now you're just unnecessarily busting my balls here with rule lawyering.  This edit updates the tagging on TIGER-imported CDPs identifed by TIGER tagging that indicates that it's a CDP.

For example:
https://www.openstreetmap.org/relation/237313

Tagged
tiger:NAMELSAD=Lakeview CDP

I scanned through enough of these with lookups to satisfy myself that these are all categorically CDPs.  I felt this was a fairly obvious tagging cleanup and consistent with our norms.  I do a lot of boundary work, it's fairly tedious and it involves a lot of lookups and corner cases.  I didn't feel it needed a discussion as these cases were clear-cut.

Now, if you feel that this edit was wrong and I've overstepped our norms for these kinds of edits, feel free to revert it and start a discussion about whether these features should be tagged as CDPs and I'll focus my ongoing boundary efforts to other areas.

I stand by this edit as correct. boundary=census is a well-established tag for CDPs in the United States.  That has been discussed ad nauseum.