I can’t speak to Logseq’s prioritization patterns, but generally speaking the Obsidian developers focus on things things that are hard for plugin developers to do, like the mobile app, or things that are “table stakes” functionality that most users can reasonably expect to have even in safe mode, like tags.
Logseq has a much larger team than Obsidian’s, which leads to different design decisions being made. Most of the time something gets pulled into Core, it’s because there’s a good reason for the feature to be core instead of a plugin.
It might help your feature request get traction if you can explain what about the current plugin is insufficient for you and why you’d like this to be in core — instead of any of the other plugins that could be pulled into core, like for instance dataview or style settings.
Developer hours aren’t infinite, so knowing more about why this matters to you will help with prioritization.