Scratch that. Just reproduced this from this import after creating a fresh reproduce.
It appears that 1.x blueprints that are loaded into 2.x do not have an active_index set. This is what is ultimately responsible for the crash. I'll get something out to protect against this. In the mean time, moving one of the blueprints within the book, or shift-scroll wheel to cycle through the book before pasting it should fix the blueprint book.
Edit: More accurately, the active index points to an un-populated slot in the book.
Edit2: Related to https://forums.factorio.com/viewtopic.php?p=680628. New, more reliable method of determining the "in-use" blueprint was added in 2.0.67. This crash should now be fixed.