Core association is forced in Playlists

Description

I created playlists with no Default Core (N/A in playlist manager). Also all my .lpl files have "DETECT" written on both core path and core name lines.

But if I load a game, say Golden Eye in my Nintendo 64 playlist with ParaLLEIL N64, it will be the default core unless I Reset the core association for each game or for each playlist in the playlist manager.

I looked at RA options for hours and search and forums and issues on here but didn't find anything about that.

Expected behavior

I want to be asked to choose a core each and every time I run a game on my playlists, just like with "Load Content'.

What would be even better, is if on the top list of suggested cores for each game, is the last used core of that playlist so that if we still want to use the same core, it'd be quick while having the choice at the same time.

Actual behavior

The last used core is set as default per game in a playlist

• RetroArch: [1.9.1]

Environment information

• OS: [Win 7 x64]

Start by reproducing the behavior through the playlist manager and the Load Content flow described in the issue, then trace where playlist and per-game core associations are selected. Done means a game prompts for a core on every launch, with the playlist's last-used core appearing among the suggested choices.