OK, you use one MCQ slide to mimick a slide with two questions. Just one tip: some of the editing of the different elements on the quiz slide can be done on the quizzing master slide. Only the individual answer objects cannot be edited there which is a pain since many versions. 

However there are several problems which you don’t mention (wisely), but would be good to announce to users curious about trying this out:

• If you want to show the default score slide, this slide will still be considered to be one question. Number of correct questions, total number of questions will not have the correct value. Several quizzing system variables which are used to transfer to the LMS will not have correct values. You showed one quizzing system variable (I suppose), cpQuizInfoPointsscored. But have a look at cpQuizInfoTotalQuestionsPerProject, cpQuizInfoCorrectAnswers?
• There is bit of a problem if you want to use penalties.
• A MCQ with partial scoring is considered to be ‘correct’ even if some correct answers have not been given. This means that the learner will be confused, if only one of the ‘two’ questions are answered, because it will be counted as partial correct. Since you don’t show the feedback messages in  the video, Captivate users watching this will not be able to know that.
• During Review, the quiz slide will be considered as one question.
• You will need to create a custom progress indicator because the default one will be awry.
• You talk about mixing types, but in reality you can only mimick T/F with MCQ, or two T/F or two MCQ. There is no way to use any other type (sequence, matching, hotspot, short answer).

If you really want multiple questions (like T/F) on one slide, the best way is to create a custom question slide, using standard objects and shared/advanced actions. There are many ways to tweak the default Quiz design (have blogs about using audio, images instead of text answers) without breaking the full functionality of default quiz slides, but this is not really a good example. That is probably the reason you avoid talking about quizzing system variables or transfer to LMS.