Not sure I’d create the region in addition to the article since it’s slightly more verbose.
I opened this issue making the case for NVDA tracking articles as regions for purposes of navigating to the next/previous landmark. Hopefully that will resolve the issue in the medium term.
Meanwhile, I opened this PR adding a non-visual second-level heading role on the post metadata field. With this patch applied to my test instance, h/H navigates between posts without headers. Admittedly this scheme breaks down if the post itself contains headers, but I’d argue that as screen reader users we’re used to that type of mixed content, and until NVDA considers articles as landmarks, having a quick way to skip to the next post is better than introducing filler regions.