Should we decouple any modules

Quiz builds on a lot of core/contrib functionality instead of reinventing (if you remember, was done for the D5-D7 versions, resulting in a mountain of technical debt).

Rules is used for evaluating all the feedback items and allows for custom conditions. Agreed it should probably move to something like ECA or core conditions.

entity - Quiz requires some Entity functionality not provided by core, e.g base entity classes/forms/handlers
range - Needed for widgets like grade range (e.g. grade between X and Y)
rules, typed_data - Needed for evaluating Feedback conditions
paragraphs - Needed for all sorts of nested data storage e.g. MCQ questions, Feedbacks, Grade feedback, Taxonomy questions...
entity_reference_revisions - Dependency of paragraphs, also powers Quiz revisioning
views_bulk_operations - Needed for admin functionality e.g. question bank, quiz questions, results
views_data_export, rest, csv_serialization - Needed for reporting/exports of Quiz results

Thanks for your detailed answer. I need to mature this a bit, but wondering if we could decouple those.
My usecase is: I want editors to create simple quizzes (probably only multianswer questions), and people (in my case anonymous, but don't think is relevant) would complete them and see how they did at the end.

Multianswer answers being paragraphs is quite a lot, but I understand the reasoning. Could be simpler though.
I won't have "evaluator" feedback (so paragraphs, rules and their dependencies are overkill for me).
I need feedback to be custom based on results (so range should be in I think).
I don't want to export the results (no views_data_export, rest, csv_serialization). Actually I was exploring how we could swap the quiz results storage, because I don't even want to store them if possible, even I understand we need those while the users are completing the quiz.

It would be a pity ending with a custom solution or a mostly-duplicated "simplequiz" module because of those constraints.

I'd be a +1 for this.

Example not sure if field_group, vbo, or data_export are needed. People could always download them and update their views or displays themselves but takes the burden off quiz.

Would need to happen in a new major release (7.0.x) and we could update the README with suggestion modules/.

Personally I'd like to decouple VBO and data export from quiz. It's 100% useful but not every site uses the export and feel if someone

I think field_group can be removed but made a dependency of quiz_multichoice. So if a site wants to install mutichoice they go out and download field_group

Same deal for range and quiz_feedback

Would have to research entity if that's needed

Paragraphs seems to be needed.

100% support replacing rules with ECA.

Thoughts?

So I am decoupling views data export. Module appears relatively unsupported and is a sole blocker for D11