Only the 301_redirects option (and 301_redirects_wildcard where present) in wp_options. Simple 301 Redirects stores every rule there as a serialised array of request_path => destination pairs. SleekView unpacks it into one row per rule and queries it like any other dataset.

No. Simple 301 reads the same option on every front-end request and issues the redirect itself. SleekView only reads the option, never writes back through a different path. Disabling SleekView leaves every existing rule firing exactly as it did before.

Yes. A Pie or Bar grouped by the wildcard flag shows the split. On many older sites the wildcard slice is tiny but is responsible for most of the actual redirect traffic, which is a useful thing to surface before a cleanup.

Yes. Group a Bar by destination with a Count aggregation and the card ranks destinations by how many rules point to them. Homepage catch-alls and over-used hubs become obvious, which is the first useful step in a redirect audit.

Roughly. Simple 301 does not store a timestamp per rule by design (the plugin is intentionally minimal), so the Area card uses the order index in the option array as a stand-in. That gives a cadence shape rather than a literal date axis, which is enough to tell waves of cleanups apart.

Yes. Any filtered view exports as CSV with request_path, destination and the wildcard flag, which is the exact shape a migration contractor needs to port the rules into Redirection, Safe Redirect Manager or a server-level rules file.

Yes, indirectly. Group by request_path with a Count aggregation; any path with a count above 1 is a duplicate definition (the plugin keeps the last one in array order). The grouping makes the conflict visible, even though Simple 301 itself has no native conflict warning.

Yes, as long as the fork stores its rule set in the same option key. Most forks (Simple 301 Redirects with Bulk Uploader, etc.) preserve the original option for compatibility, so the dashboard works against them without configuration. If a fork uses a different option, the dashboard can be pointed at that option name instead.