ShaunBuckingham  I probably was not clear. The process is the same (or should be) as adding an item to the list through the "add an item" button. We are essentially not adding the item itself via Power Automate, but instead making that same link to it. My concern is that using a Power Automate "add item to list" action, does not invoke the same scripted actions that are supposed to happen behind the scenes to format and prep the data for the layout and purpose of the Playlist. Instead, it appears that adding through PA, only adds the item's info (or at least the columns that are required/the user has opted to fill within the PA flow), and then it skips everything else built into the Playlist list. If you don't have backstory on how custom list templates  work, there is good documentation that MS has at https://learn.microsoft.com/en-us/sharepoint/lists-custom-template. Essentially you can package in PowerAutomate flows WITHIN a custom list template. These flows invoke during certain events (like when an item is added) so that custom formatting that the layout NEEDS is properly taken care of and the end user doesn't have to worry about such things. I just don't have the right logs/insight into knowing if adding items through PowerAutomate actions is invoking those private flows in the Playlist template. I assume not since it's all FUBAR afterwards! 🙂
And to your point, I don't know if I'd want the whole item be added to the list. Lists are supposed to be lightweight and the framework they live on is not meant to handle huge amounts of data (like video content). Thus the library being the file storage and the list/playlist being the UI/pointer seems the right combination to keep.